microsoft / microsoft/monaco-editor
[Bug] workerMain.js could not be fetched because of an invalid URL
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46.8k
- Forks
- 4.1k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 1
Description
Reproducible in vscode.dev or in VS Code Desktop?
- Not reproducible in vscode.dev or VS Code Desktop
Reproducible in the monaco editor playground?
- Not reproducible in the monaco editor playground
Monaco Editor Playground Link
Monaco Editor Playground Code
const tsCode = `
// Typescript
const f = async function () {
alert('hi');
};
`;
// Hover on each property to see its docs!
const myEditor1 = monaco.editor.create(document.getElementById("container1"), {
value: tsCode,
language: 'typescript',
automaticLayout: false,
});
Reproduction Steps
Just loading the provided playground URL in the browser should be enough.
Actual (Problematic) Behavior
"The browser fails to load the workerMain.js file because it attempts to fetch it from 'https://microsoft.github.io/node_modules/monaco-editor/min/vs/base/worker/workerMain.js#editorWorkerService' instead of the correct URL 'https://microsoft.github.io/monaco-editor/node_modules/monaco-editor/min/vs/base/worker/workerMain.js#editorWorkerService'.
In other words, the URL needs to be absolute rather than relative.
Check the browser console for more info."
Expected Behavior
The resource should be fetched.
Additional Context
This bug is specific to the playground.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the provided Monaco Editor Playground URL and inspect how the playground requests workerMain.js. Compare the failing relative URL with the expected /monaco-editor/ path, then verify in the browser that the worker resource loads without a console error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100