Error loading extensions

[Sammy-T]

I've been trying to load extensions. I can see that it correctly loads the languages and grammars contribution files and provides proper syntax highlighting. But I encounter errors if it tries to load extension logic.

Here's an example of what I've got so far testing with json extensions https://github.com/Sammy-T/monaco-err/blob/master/src/main.js

Am I missing or misunderstanding something?

[CGNonofr]

I'm not sure what you are trying to achieve loading those json and json-language-features default extensions by hands while this library already bundles them for you 🤔

You should have a look at your terminal though, there are errors, and those errors are related to your issue. Vite handles the new URL(..., import.meta.url) syntax only if the first parameter (the path) is a literal.

[Sammy-T]

To clarify, I'm using those json extensions for testing. Ultimately, I'd like to be able to load extensions dynamically.

And I'm not sure what you mean about the new URL() syntax. Are you seeing something I'm not? I'm not seeing errors retrieving and registering the package.json files or any of the files referenced within them. The syntax highlighting provided by the first json extension appears to be working just fine.

And yeah, I can see that one of the errors points to nativeImportScripts() within a bootstrapFn() which I'm finding difficult to get a better understanding of since it exists inside a blob.

[CGNonofr]

Ultimately, I'd like to be able to load extensions dynamically.

What do you mean by dynamically? if you mean being able to load them at any moment, that's already doable by importing the package dynamically whenever you want

And I'm not sure what you mean about the new URL() syntax. Are you seeing something I'm not?

You are doing new URL(importPath, import.meta.url).toString() (l105), how do you expect vite to be able to add that assets to the final bundle? it needs a literal path.

[Sammy-T]

By dynamically I meant loading a potentially variable path of an extension without necessarily knowing which extension beforehand.

You are doing new URL(importPath, import.meta.url).toString() (l105), how do you expect vite to be able to add that assets to the final bundle? it needs a literal path.

Lol. I see what you mean. I wasn't planning on using that for the final build but I did forget that vite doesn't like that. Thanks.