Selectize.js: npm package should not have "dependencies", just "devDependencies"

Created on 9 Dec 2016  路  11Comments  路  Source: selectize/selectize.js

We want to install the 'selectize' npm package just to get access to dist/selectize.js - i.e. we want to use the package similarly to the way you use it from bower (without browserify/webpack).

Currently package.json contains:

  "dependencies": {
    "jquery": "^1.7.0",
    "microplugin": "0.0.3",
    "sifter": "^0.5.1"
  }

We don't want to install any of these, and sifter is a problematic dependency because of the transient C++ dependency.

It would be useful to either have this changed, or publish a new npm package without production dependencies.

All 11 comments

In my understanding, dependencies are packages you need to run the library, devDependencies being packages you need to work on improving the library. Hence, we're saying Selectize cannot be ran without packages Jquery, Microplugin and Sifter.

Can you walk me through your logic?

Dependencies are the packages you actually require() in node sense, not packages you need to have loaded up by

ran into exactly the same issue today. coming from Bower. I was surprised by the 16 dependencies pulled in due to the sifter and microplugin dependencies - as we're including just the standalone dist files from selectize directly in a <script> tag.

Just adding my thoughts that a correct package.json without the unneeded dependencies would be nice. I am not sure why the change is significant as it will just be removing the dependencies section from package.json. None of the listed items are dependencies in the typical NPM sense, as @vivainio explained.

@vivainio: Dependencies are the packages you actually require() in node sense, not packages you need to have loaded up by

Related issues

Wardrop picture Wardrop  路  19Comments

Saeven picture Saeven  路  15Comments

jbrooksuk picture jbrooksuk  路  42Comments

arathael picture arathael  路  33Comments

nepsdotin picture nepsdotin  路  15Comments