Replies: 1 comment 4 replies
-
|
Hi @kaisalmen, only solution I found so far is to update the fetch function, but this is not ideal :( const originalFetch = window.fetch;
window.fetch = async (input, init) => {
if (typeof input === 'string' && input.startsWith('data:')) {
// decode inline data URIs locally (avoids CSP connect-src issue)
const [, rest] = input.split(',');
const decoded = atob(rest);
return new Response(decoded, { status: 200 });
}
return originalFetch(input, init);
};Any other solution that might work in this case? |
Beta Was this translation helpful? Give feedback.
-
|
@dhrubomoy sorry, I am no webpack expert and currently don't have an idea. Is vite/rollup not an option for the bundling or are you required to use webpack? |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately no, trying to integrate the editor in production and we use microfronted architecture with webpack :( |
Beta Was this translation helpful? Give feedback.
-
|
@dhrubomoy thank you. If you find a solution or solutions to your webpack problems, we could update our config here as well. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @kaisalmen, Posted the question to the monaco-vscode-api repo as well. Basically it was an issue with webpack. "A file with size less than 8kb will be treated as a inline module type". I had to add following to my webpack cofig to treat it as {
test: /\.json$/i,
type: "asset/resource",
}But even that was not enough. Had to use emmited file urls when setting the extensions in the - import statemachineLanguageConfig from './language-configuration.json
- import responseStatemachineTm from '../syntaxes/statemachine.tmLanguage.json
+ import responseStatemachineTmUrl from '../syntaxes/statemachine.tmLanguage.json?url';
+ import statemachineLanguageConfigUrl from './language-configuration.json?url';
- extensionFilesOrContents.set(`/${params.languageServerId}-statemachine-configuration.json`, statemachineLanguageConfig);
- extensionFilesOrContents.set(`/${params.languageServerId}-statemachine-grammar.json`, responseStatemachineTm);
+ extensionFilesOrContents.set(`/${params.languageServerId}-statemachine-configuration.json`, new URL(statemachineLanguageConfigUrl, window.location.href));
+ extensionFilesOrContents.set(`/${params.languageServerId}-statemachine-grammar.json`, new URL(responseStatemachineTmUrl, window.location.href)); |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am using webpack to bundle a langium based editor very similar to the statemachine example in this repo. I am trying to define some custom themes in the extension and set the theme. Here is how I did it.
It works great in this example, it is using vite. But when I try to bundle using webpack and use it in a single page application, I encounter error
Uncaught (in promise) Error: Unable to load extension-file://my-script.my-script-editor-extension/extension/my-script-my-script-dark-theme.json: Failed to fetchI have followed instructions from this doc to bundle the workers, and it works well. But when setting the theme I get the error.
I was wondering if this is a known issue. And if there is a way to fix it or if there is a better way to use custom theme?
Here is the full console error:
Beta Was this translation helpful? Give feedback.
All reactions