Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Description

None

Environment

None

Attachments

1
  • CLJS-1973.patch
    CLJS-1973.patch
    12 Mar 2017, 06:21 AM

Activity

Show:

David Nolen March 18, 2017 at 5:23 AM

Thomas Heller March 12, 2017 at 7:19 PM

Wrote about this in Slack but I wanted to properly voice my concerns so they don't get lost in Slack archives.

I think managing npm via CLJS is a bad idea. While this is very interesting it could/should probably happen in a library. We will inherit all the woes npm brings and force this onto the user. What if the user prefers yarn? What if the user is using a tool with support for package.json but not deps.cljs?

I voiced similar concerns a while ago [1] and with everything happening recently with regards to JS modules the situation is getting worse. It may appear that this work must happen in CLJS but really could happen somewhere else without making cljs.core more complicated. clojure.core doesn't bundle with leiningen for good reason.

IMHO, YMMV

[1] https://groups.google.com/d/msg/clojurescript/xMQuEmQt7oQ/AWT5RZe_nQQJ

Completed

Details

Assignee

David Nolen

Reporter

Patch

Code

Fix versions

Priority

Created March 12, 2017 at 6:15 AM
Updated March 18, 2017 at 5:23 AM
Resolved March 18, 2017 at 5:23 AM