trent

Here's where I'd ultimately like to see Vue attribute scopes endup. I'd be welcome to break these out as separate issues, so they can be tracked as smaller units of...

Additionally, for this example: ```jsx const prismIncludeLanguages = (Prism) => { // ... additionalLanguages.forEach((lang) => { require(`prismjs/components/prism-${lang}`); // eslint-disable-line }); require('/path/to/your/prism-language-definition'); // ... }; ``` 1. `{` on line 1...

@ymassad According to the proposal, your example is correct but possibly not for the reasons that you expect. Here is an example that might make things a little clearer. ```csharp...

@ymassad Sorry. I meant to write this. ```csharp [SomeAttribute] public void DoSomething(B input) { } ``` I believe this is the spec.

> I see this working in the scss and less grammar. Are you sure it's an issue with the vscode-textmate engine? I'm having trouble finding the situation in those grammars....

I believe I'm seeing the same symptom. I'm just not sure if the cause is the same. Here is my reproduction: https://github.com/roydukkey/moist/tree/vite/issue-11012

https://github.com/lerna/lerna/blob/13c80ae5820ee6130d5872daa7b6e697672e3f21/libs/commands/publish/src/index.ts#L1124-L1126 Actually, I wonder too if the preceding conditionally never gets the configuration from the following code: https://github.com/lerna/lerna/blob/13c80ae5820ee6130d5872daa7b6e697672e3f21/libs/commands/publish/src/index.ts#L297-L306 I do see this log for the my configuration, but [this conditional](https://github.com/lerna/lerna/blob/13c80ae5820ee6130d5872daa7b6e697672e3f21/libs/commands/publish/src/index.ts#L1124-L1126)...

I think the suggestion from the Vite team would be to use [a `public` directory](https://vitejs.dev/guide/assets.html#the-public-directory). Say you have the file `/public/cool-font.woff` that was included in your Vue component library: ```vue...

For example, with `npm run test -- --arg1` and `yarn run test --arg1`.

Yes. I remember reading that before liking this issue. I don't remember exactly the "real" example that produced the warning, but I do remember it was something like I have...