-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Order packages by name #22
Comments
Do you mean to say that |
Yes. Every |
Generating a |
Well, having the package list sorted alphabetically is very nice for the developer's eyes. In our project we have over 40 npm packages. Scanning through these when not sorted is a pain. If that list were sorted, we would save some seconds looking for packages. Makes it easier to visually parse the file. In regards to modifying a source, I do not see a problem here because adding a new npm package requires a new line in the project.clj and that file has to be modified anyway. |
For all users who aren't adding a new dependency, this would modify their On Thu, Feb 19, 2015 at 3:22 PM, Michael Heuberger <[email protected]
|
Not entirely correct. package.json is only modified when you append the |
I'm OK with that. It was not clear to me from your description that an implicit flag was necessary for modifying the file. On Fri, Feb 20, 2015 at 2:25 PM, Michael Heuberger
|
Great. Sorry for not mentioning the |
You are more than welcome to contribute a pull request. Unfortunately, I On Fri, Feb 20, 2015 at 4:06 PM, Michael Heuberger <[email protected]
|
Thanks man. I am afraid I do not know any Clojure. Writing all the code in JavaScript here at work. Take your time to implement this. There is no rush. I'd say, low priority ;) |
Well Michael, despite being OK with the interface, unless there is higher demand for this feature I'd rather not implement it. On Fri, Feb 20, 2015 at 10:13 PM, Michael Heuberger
|
that's fine - as i said before: low priority for now. |
Currently when you do a direct
npm install
, it sorts the dependencies by name in the package.json. Do you think you could do the same here? That would be great. ThanksThe text was updated successfully, but these errors were encountered: