We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
monaco-editor version: 1.10.1 Browser: Chrome OS: OSX
Steps or JS usage snippet reproducing the issue:
Bundling tools (such as webpack or parcel) attempt to load source-maps when referenced within JS files - and throw warnings when not found.
The monaco-editor source that is published to NPM contains references to source-maps that are not included within the package.
monaco-editor
For example, here is a sample warning (of hundreds) emitted by Parcel when trying to bundle monaco:
⚠️ Could not load existing sourcemap of "../../node_modules/monaco- editor/esm/vs/language/json/_deps/vscode-json-languageservice/utils/json.js".
This is pointing to the following file, which contains this reference as the last line:
//# sourceMappingURL=json.js.map
The json.js.map file that it is expecting as a sibling has not be included on the published NPM package.
json.js.map
The text was updated successfully, but these errors were encountered:
d3fdf3b
alexdima
No branches or pull requests
monaco-editor version: 1.10.1
Browser: Chrome
OS: OSX
Steps or JS usage snippet reproducing the issue:
Bundling tools (such as webpack or parcel) attempt to load source-maps when referenced within JS files - and throw warnings when not found.
The
monaco-editor
source that is published to NPM contains references to source-maps that are not included within the package.For example, here is a sample warning (of hundreds) emitted by Parcel when trying to bundle monaco:
This is pointing to the following file, which contains this reference as the last line:
The
json.js.map
file that it is expecting as a sibling has not be included on the published NPM package.SOLUTION:
Thanks! 🍰
The text was updated successfully, but these errors were encountered: