Update to google-closure-compiler@20240317.0.0
#96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #97
👋 We (VS Code) are in the process of moving to ESM (microsoft/vscode#166033) and are running into an issue when loading
jschardet.min.js
into our node.js environment. The error was no longer reproducible when moving to a newer version ofgoogle-closure-compiler
, in fact even just the next versionv20151216
fixes it.The error we see is when attempting to load
jschardet.min.js
with a custom loader we implement to bridge between ESM and CommonJS/AMD. The error is:There is more context in microsoft/vscode#160416 (comment) and onward.
I think with newer versions of
google-closure-compiler
some polyfills are no longer applied that maybe lead to this issue 🤔Curious why this project has never updated this dependency to a later version. With this PR the latest version is picked and obviously the change in
jschardet.min.js
is rather large. Is there a way to validate this works in all environments?