Break out dependencies?

[kevinburkeshyp]

As a rough measure of how "big" the project is in terms of dependencies, when shrinkwrapped bootprint-openapi has 2000 lines of dependencies, and roughly 500 distinct packages.

Is there anything that can be done to reduce the size or scope of what must be installed to use this project?

[nknapp]

Are you talking about devDependencies or dependencies.
The only normal dependency is actually bootprint-json-schema which uses bootprint-base.
bootprint-base uses

• marked: For markdown processing
• json-stable-stringify: To render examples in a stable fashion
• hightlight.js: To allow code-highlighting in markdown texts and to highlight JSON-examples.
• cheerio: For postprocessing HTML generated by marked
• handlebars: Mostly to use Handlebars.SafeString for HTML generated by marked
• bootstrap: To include the boostrap-less-files.

I don't think that there is a lot to be left out. If you have any ideas, go ahead and tell me. I would also like to reduce the overall size of the packages.
I have tried to encourage some of the dependency-maintainers to add a files-section to their package.json to reduce the size of the dependencies, but that hasn't always been heard.

The dependency-tree for the production files isn't actually that big.

└─┬ bootprint-openapi@0.15.0 
  ├─┬ bootprint-json-schema@0.8.6 
  │ └─┬ bootprint-base@0.7.2 
  │   ├── bootstrap@3.3.6 
  │   ├─┬ cheerio@0.19.0 
  │   │ ├─┬ css-select@1.0.0 
  │   │ │ ├── boolbase@1.0.0 
  │   │ │ ├── css-what@1.0.0 
  │   │ │ ├── domutils@1.4.3 
  │   │ │ └── nth-check@1.0.1 
  │   │ ├─┬ dom-serializer@0.1.0 
  │   │ │ └── domelementtype@1.1.3 
  │   │ ├── entities@1.1.1 
  │   │ └─┬ htmlparser2@3.8.3 
  │   │   ├── domelementtype@1.3.0 
  │   │   ├── domhandler@2.3.0 
  │   │   ├── domutils@1.5.1 
  │   │   ├── entities@1.0.0 
  │   │   └─┬ readable-stream@1.1.13 
  │   │     ├── core-util-is@1.0.2 
  │   │     ├── inherits@2.0.1 
  │   │     ├── isarray@0.0.1 
  │   │     └── string_decoder@0.10.31 
  │   ├─┬ handlebars@3.0.3 
  │   │ ├─┬ optimist@0.6.1 
  │   │ │ ├── minimist@0.0.10 
  │   │ │ └── wordwrap@0.0.3 
  │   │ ├─┬ source-map@0.1.43 
  │   │ │ └── amdefine@1.0.0 
  │   │ └─┬ uglify-js@2.3.6 
  │   │   ├── async@0.2.10 
  │   │   └── optimist@0.3.7 
  │   ├── highlight.js@8.9.1 
  │   ├─┬ json-stable-stringify@1.0.1 
  │   │ └── jsonify@0.0.0 
  │   └── marked@0.3.5 
  └── lodash@3.10.1 

Now, the dependency-tree of bootprint is huge, I agree. And that is not a good thing. But a large portion is covered by

• the less-compiler, which is essential
• chokidar: This is the file-watcher used in development-mode. I had the feeling it's the best one, but maybe there is a smaller one (gaze??). But a file-watcher should definitely be in there.
• live-server: If you find another live-reload-capable embedded http-server for use in development-mode let me know. It also has plenty of dependencies.

Maybe it is possible, to use watchr as a dependencies of customize-watch instead of chokidar. watchr is already used by live-server so it is in the node_modules and can be reused (with npm>=3).

Oh and: I have intentionally split bootprint-openapi in bootprint-openapi, bootprint-json-schema and bootprint-base to allow reuse for other purpose. I have also intentionally split up the functionality of bootprint into all the customize-* packages, also to be able to reuse them.

Of course, this adds dependencies, if you just count the lines of the npm ls-output. But it does not add code.

[nknapp]

It might be helpful here to break out the dev-mode (file-watcher and live-server) into a separate package, so that dev-mode option only works, if this package is present as well. It would reduce the size of the bootprint-core which is probably used by more people than the dev-mode.