You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone,
I'm looking for a proper way to deploy NodeJS apps to end-users without having to bundle everything in one single package. Like a Stub, a small binary/script that will download all dependencies to the end-user's computer. (Eg. Firefox stub download)
Putting everything in a single package like some do is all wrong.
The user will be downloading a package containing the main app scripts + nodejs binary + node_modules dependencies. Which in the end, will all be outdated unless the developer/publisher keeps his package updated constantly. Not to mention a layman user wouldn't know how to handle the package.
Is it there a stub/script/wizard that does that?
The logic I think
Download the core script app (Only the actual script/app files without the node_modules folder)
@rumkin is correct, this kind of general question is better suited for other places, such as the nodejs/help issue tracker. This issue tracker is for node core-specific bug reports, feature requests, etc.
Hello everyone,
I'm looking for a proper way to deploy NodeJS apps to end-users without having to bundle everything in one single package. Like a Stub, a small binary/script that will download all dependencies to the end-user's computer. (Eg. Firefox stub download)
Please refer to: http://stackoverflow.com/questions/42609945
Putting everything in a single package like some do is all wrong.
The user will be downloading a package containing the main app scripts + nodejs binary + node_modules dependencies. Which in the end, will all be outdated unless the developer/publisher keeps his package updated constantly. Not to mention a layman user wouldn't know how to handle the package.
Is it there a stub/script/wizard that does that?
The logic I think
I wrote two nice nodeJS apps but I don't know how to publish them properly.
Please, have your say!
The text was updated successfully, but these errors were encountered: