Project files autoreloading from https://esm.sh/modern-monaco@0.2.2/es2022/editor-core.mjs

[jadedevin13]

Even if you change tmDownloadCDN. It's auto reloading again to esm.sh.

The modern-monaco package itself should not use external CDN as it's already loaded on the app.

[jadedevin13]

Lol. I can't test it, somehow if I load it in my project. It's autoreloading it in https://esm.sh/modern-monaco@0.2.2/es2022/editor-core.mjs. and blocking esm.sh stops everything from working.

Originally posted by @jadedevin13 in #35 (comment)

[jadedevin13]

Also related

Hi, thanks so much for this awesome library — we’re excited about the possibility of integrating it into our platform!

We’ve noticed that the current setup appears to rely heavily on the CDN at esm.sh. For security and compliance reasons, our customers are very strict about the domains we can allow, and introducing a new third-party CDN can be problematic.

Would it be possible to self-host the entire library (without any interaction with external CDNs) so we can serve everything from our own infrastructure?

This isn’t a hard blocker — more of a “nice to have” — but support for self-hosting would make a big difference for us and would mean a lot.

Thanks again for your great work!

#31 (comment)

[jadedevin13]

Solved by adding

<script type="importmap"/> to document.

see

modern-monaco/src/core.ts

Lines 357 to 365 in b67ca74

	if (importmap = document.querySelector("script[type='importmap']")) {
	try {
	const { imports = {} } = parseImportMapFromJson(importmap.textContent);
	if (imports["modern-monaco/editor-core"]) {
	editorCoreModuleUrl = imports["modern-monaco/editor-core"];
	}
	if (imports["modern-monaco/lsp"]) {
	lspModuleUrl = imports["modern-monaco/lsp"];
	}