Skip to content
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

Open
ptusch opened this issue May 31, 2017 · 3 comments
Open

Support for library only projects? #39

ptusch opened this issue May 31, 2017 · 3 comments

Comments

@ptusch
Copy link

ptusch commented May 31, 2017

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?

@pmq20
Copy link
Owner

pmq20 commented Jun 5, 2017

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 libsquash glues the internal require's together in the back scene.

One restriction is that your library must only have exactly one entrance. Impossible to require your_library/a first then your_library/b.

@ptusch
Copy link
Author

ptusch commented Jun 6, 2017

I think that is a fair restriction since assumptions to the internal structure of a package seem rather untidy.

@pmq20
Copy link
Owner

pmq20 commented Jun 7, 2017

@ptusch Added to 2.x roadmap: https://github.com/pmq20/node-compiler/blob/master/ROADMAP.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants