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
Now that 2.1.2 has a file cache, there are some dynamic build situations, particularly for web-based builders, where the string contents of a file could be auto-generated. Ideally these strings could be seeded into the file cache on each optimizer run.
Then, in jslib/build.js, once config is set in the requirejs context, but before the first require() for modules happens, go through the rawText list, call require.toUrl to get urls for those IDs, and seed require._cachedRawText with the text values.
The text was updated successfully, but these errors were encountered:
Now that 2.1.2 has a file cache, there are some dynamic build situations, particularly for web-based builders, where the string contents of a file could be auto-generated. Ideally these strings could be seeded into the file cache on each optimizer run.
Consider a build option that looks like this:
Then, in jslib/build.js, once config is set in the requirejs context, but before the first require() for modules happens, go through the rawText list, call require.toUrl to get urls for those IDs, and seed require._cachedRawText with the text values.
The text was updated successfully, but these errors were encountered: