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
Projects using native ECMAScript modules could use a command line flag to limit closure-calculate-chunks to only following ESM imports (import, import(), and export * from), and to ignore require(), 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:
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.
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: