-
Notifications
You must be signed in to change notification settings - Fork 1
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
Option for pure-ESM mode #10
Comments
Do you have an example of the problematic code? The only goal of this project is to identify the correct source set and allocate the files to the correct output chuck for feeding into closure-compiler. If you have discoverable code that is not actually intended to be included in the compilation, there is not currently an option to exclude it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Projects using native ECMAScript modules could use a command line flag to limit closure-calculate-chunks to only following ESM imports (
import
,import()
, andexport * from
), and to ignorerequire()
,goog.require()
, and the like.Code that uses the imperative RequireJS API for loading external libraries at runtime can cause tracebacks when closure-calculate-chunks attempts to parse them.
The text was updated successfully, but these errors were encountered: