Expose vite dev server plugin?

[kaisalmen]

@CGNonofr Is it possible to expose the vite dev server import.meta.url workaround plugin as another npm sub export of monaco-vscode-api?

I have copied an now outdated version and used it at different places. I also just realized that when people used vscode default-extension in a vite dev server they all have the same problems. It is easier to tell them, please use this sub export from monaco-vscode-api instead of copying code that gets outdated. WDYT?

[CGNonofr]

Either that or a library of its own since it's not really specific to this library! or even opening a PR to integrate it directly in vite? :D what do you think?

[kaisalmen]

or even opening a PR to integrate it directly in vite? :D what do you think?

Yeah, why not. If that takes too long or they don't want it, then plan B.

[CGNonofr]

I just had a look at it and it seems pretty easy

[CGNonofr]

Do you mind doing it?

[kaisalmen]

Isn't it easier you do it, because you created it?

[CGNonofr]

=> vitejs/vite#14260

[kaisalmen]

@CGNonofr nobody is interested in your PR? ⬆️

[CGNonofr]

@CGNonofr nobody is interested in your PR? ⬆️

😢

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[kaisalmen]

Let's leave this open until there is a clear way forward in the linked issue, ok?

[CGNonofr]

Is there another way than posting a new comment every 3 days ?

[kaisalmen]

Is there another way than posting a new comment every 3 days ?

Don't know. 😆 Then let's close this.

[CGNonofr]

It seems there is a way to ignore issues with a label, I'll do something