Scope the `custom-elements-manifest.mjs` to a directory and ignore itself.

[KonnorRogers]

Shopify/ruby-lsp#2918

Sometimes I'm working on repos without the analyzer, and creating the custom-elements-manifest.mjs can be quite disruptive.

could we do something like:

.cem_lsp
|-- .gitignore
|-- custom-elements-manifest.config.mjs

and in the .gitignore have the following: *

happy to make a PR if you're open to it.

[Matsuuu]

Hi Konnor, long time now see uhm talk ehh write!

I like the idea and am open to supporting it. I've not had much time to put into this project as of late but am planning on picking up the slack come next year.

I took a look at https://github.com/Matsuuu/custom-elements-language-server/blob/main/lib/custom-elements-languageserver-core/src/cem/analyzer.ts#L161-L198 , and from what I've gathered from the ancient hieroglyphs I've written ages ago, this should already be supported..?

Can you try out using a cem config like your proposal and report back if it works?

[KonnorRogers]

Hi there! It has been a while!

and im not talking about my own manifest, for some reason the language server is generating this file for me, even when I have custom-elements-manifest.js in my repo. Which as i look at it now, may not be detected by the LSP 🤔

[Matsuuu]

I think due to how vscode works, I'm forced to use mjs files for configuration at least in the current version. There was some really iffy stuff that stopped me from utilizing all js file configs but I could look into it now with fresh eyes. That might be the reason it's not noticing your file.

---

Looking at the code, I can't even remember writing this workaround but noticed it: https://github.com/Matsuuu/custom-elements-language-server/blob/main/lib/custom-elements-languageserver-core/src/cem/analyzer.ts#L135-L152

It generates the mjs version for the plugin to parse, and should delete it after that, but seems like there's something stopping the plugin from deleting it, therefore it not being deleted.

As for remedies to your trouble right now, I'd recommend trying to port your .js config to mjs for now, if possible. That should resolve some of the issues for now.

I am currently in the middle of a huge crunch period at our company so time for this project is extremely limited, but I'll try and find some time to work on this in the coming month or two.