-
Notifications
You must be signed in to change notification settings - Fork 202
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
Support for library only projects? #39
Comments
Very good idea. My thinking is that we can compile your library into a binary form, allowing the user to require one single module and fetch all functionalities of the original library, while One restriction is that your library must only have exactly one entrance. Impossible to |
I think that is a fair restriction since assumptions to the internal structure of a package seem rather untidy. |
@ptusch Added to 2.x roadmap: https://github.com/pmq20/node-compiler/blob/master/ROADMAP.md |
Good day,
I was wondering if you are planning to add support for "library only" modules and let them be included using the bindings modules or similar ones.
This would a pretty cool feature for anyone who is planning to deploy his library without any direct executable code.
What are you thoughts?
The text was updated successfully, but these errors were encountered: