-
Notifications
You must be signed in to change notification settings - Fork 46
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
Consider using npm deps instead of submodules #109
Comments
Just for fun, doing
is totally doable. Future of npm for frontend: http://blog.npmjs.org/post/101775448305/npm-and-front-end-packaging This doesn't mention the idea I might want some magic way to use package.json without running "npm install". [P.S. the "Deferred" label is here for a reason. As much as all this is tempting to experiment & bikeshed, it's an entirely separate project from Mathdown.] |
For Heroku, it's probably possible to support submodules with all flows via a buildpack. |
package.js can point to arbitrary git urls.
Platforms like Heroku, OpenShift, Travis already run
npm install
on deploy.npm install
either.npm install; npm start
would be "one less tool", but "one more tool" for devs who have git but not Node and directly openfile:/.../index.html
. It's not obvious I'll be able to keepindex.html
on par withnpm start
anyway (cf. [semi] protect system pages (about, help) #101).Crazier ideas:
node_modules
or eachnode_modules/foo
could be a submodule pointing to some auto-generated repo./CodeMirror/
, they just have to load.handy reference: https://github.com/wilmoore/frontend-packagers
The text was updated successfully, but these errors were encountered: