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
{{ message }}
This repository was archived by the owner on Oct 17, 2020. It is now read-only.
Generated are JS files that bundler 3 created to feed them to webpack and make everything glue together. Right now they are:
webpack configuration (it is created in memory and passed to webpack, but the bundlers writes it for diagnostic purposes only)
export entry point JS files: one file per entry point where we simply do a require to bridge AMD and webpack's bundle.
An example of 2 would be:
__MODULE__.exports=require('recharts');
This "magic" code will be processed by webpack and the require will end up transformed to a webpack_require that resolves to a module defined inside the webpack bundles.
The MODULE on the other hand, will be bound by the bundler (when AMD-wrapping the webpack bundles) in the final output so that the return from webpack_require is exported through our AMD loader.
It' the same scheme we use when adapting native framework apps.
izaera
pushed a commit
to izaera/liferay-js-toolkit
that referenced
this issue
Mar 10, 2020
Bundler 3 is generating files in three directories:
In order to maintain compatibility with bundler 2 we may want to map output as:
So we'll provide a
work-dir
config option to do this.The text was updated successfully, but these errors were encountered: