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
I'm struggling with an error with the library @codemirror/lang-xml. After I add it to my visual, I start receiving this error during compilation:
ERROR in ./node_modules/@lezer/lr/dist/index.js 1039:23-30
Module not found: Error: Can't resolve 'process/browser' in '<PATH>/node_modules/@lezer/lr/dist'
Did you mean 'browser.js'?
BREAKING CHANGE: The request 'process/browser' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
I found several solutions that involve adding a custom configuration to webpack.config.js, which we can't do, right?
Do you have any suggestions?
Thanks!
The text was updated successfully, but these errors were encountered:
Since this repository is open-source:
a) You can fork it and address the issue if it’s specific to your use case.
b) Alternatively, you can submit a Pull Request with a fix, and we’ll review and merge it if everything checks out.
If none of these options work for you, it would be helpful to see the source code that reproduces the issue. This would allow us to debug and address it in the future.
Thanks for you reply. TBH, I don't want to create a separate tool just for this. I prepared a very simple custom visual you can use to reproduce the error. Please take a look at this repo: https://github.com/danieleperilli/test-custom-visual-with-cm
I'm struggling with an error with the library
@codemirror/lang-xml
. After I add it to my visual, I start receiving this error during compilation:I found several solutions that involve adding a custom configuration to webpack.config.js, which we can't do, right?
Do you have any suggestions?
Thanks!
The text was updated successfully, but these errors were encountered: