-
-
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
Node bundling #131
Comments
Hi, @mrvicadai. Thanks for the request! Unfortunately, it is impossible in the fastpack at the moment. We've been targeting browsers first. There are some builtin (not pluggable) features which prevent an easy addition of the
If I understand the feature request correctly, for the |
I'm also interested in targeting node. Another difference that comes to mind is |
Hi @zindel thanks for the reply! I think you're correct that (1) and (2) are preventing node environment from working. Not necessarily (3) though since the application might need different configuration profiles depending on the environment. @juancampa also made a good point that |
@juancampa @mrvicadai could you suggest a reasonably simple (but still with some dependencies) app we could use for testing? |
@zindel I was looking at the source tree of the In terms of real world example, I can think of this one as reasonably small, but very frequently used node package: https://github.com/isaacs/rimraf/blob/master/rimraf.js |
Also what could be interesting for (2) is that we have a way to ignore some require() to be considered. See https://arunoda.me/blog/ssr-and-server-only-modules for an example. Webpack have its IgnorePlugin for this purpose. |
Other bundlers (like webpack) can target node environment instead of browser. That largely involves leaving things like
require('fs')
and process intact in the code.Is there a way to do the same in
fastpack
?If no, is it on the roadmap?
The use case is when writing a Node application using ReasonML, but don't want to bring the compiler with it when deploying, therefore need to bundle the js code.
The text was updated successfully, but these errors were encountered: