I'm correct, that this is only concerned with .vue files, aka single-file components?

Yes, exactly.
It would be the first step to introduce support in netbeans.

Apart from the two remaining comments from yesterday, I forgot to add:

• the javascript2.vue module should be added to the dependency list of javascript2.kit, so that it gets activated together with it
• the spec versions of the modules, that gained changed friends, should be bumped (yeah I know this is under discussion, but we are still weaks from branch point, so should not be problematic).

the spec versions of the modules, that gained changed friends, should be bumped (yeah I know this is under discussion, but we are still weaks from branch point, so should not be problematic).

The timing related to branch points has nothing to do with the problematic aspects of this. The problem occurs if there's a need to revert any feature during branch. That discussion is for another place - personally I'd prefer no spec change in any feature PR, but not stopping it.

The other thing to consider looking at this, but also probably not to resolve here, is that the number of friend dependencies in web.common is ridiculous!

Apart from the two remaining comments from yesterday, I forgot to add:

• the javascript2.vue module should be added to the dependency list of javascript2.kit, so that it gets activated together with it
• the spec versions of the modules, that gained changed friends, should be bumped (yeah I know this is under discussion, but we are still weaks from branch point, so should not be problematic).

Ah, yes, my bad, I got inspired from "jade" implementation, and I included webcommon, and css.editor without checking if it's really used.
I've removed them + removed the used friend dependencies spec version.
Thanks.

@haidubogdan awesome!!! Thx for this great enhancement. I would like to suggest some more things for this MVP.

1. Please change the icon for a more common one. It is just the V that everyone knows it from using vue: https://www.google.com/search?sca_esv=c4730c0d5f6ba8e9&rlz=1C1GCEA_deDE1066DE1066&q=vue&udm=2. Of course we need to find a licensed image that fits. The extension and this icon should be enough to recocknice it and it fits better in the NetBeans icon set.
2. Could you pleaes also add more default support like TypeScript, sass, less, scss? NetBeans also can handle all of them more or less good so those should be added as defaults for the first run as wall. I think jade maybe too? I also think that jade/pug should work in the lang attribute for the template but I'm not sure.

@haidubogdan awesome!!! Thx for this great enhancement. I would like to suggest some more things for this MVP.

1. Please change the icon for a more common one. It is just the V that everyone knows it from using vue: https://www.google.com/search?sca_esv=c4730c0d5f6ba8e9&rlz=1C1GCEA_deDE1066DE1066&q=vue&udm=2. Of course we need to find a licensed image that fits. The extension and this icon should be enough to recocknice it and it fits better in the NetBeans icon set.
2. Could you pleaes also add more default support like TypeScript, sass, less, scss? NetBeans also can handle all of them more or less good so those should be added as defaults for the first run as wall. I think jade maybe too? I also think that jade/pug should work in the lang attribute for the template but I'm not sure.

Sure, I will give it a try.
Embeddings can be picky for some languages and I hope the parametric lang lexer to go smooth.

@haidubogdan this looks good to me. Of course more could be done, but I suggest to ensure this gets in and is not lost in the quest to do more. Would you please squash the commits into one? Once that is pushed, I'll reauthrorize running unittests and once they come back clean, I'd merge.

@haidubogdan this looks good to me. Of course more could be done, but I suggest to ensure this gets in and is not lost in the quest to do more. Would you please squash the commits into one? Once that is pushed, I'll reauthrorize running unittests and once they come back clean, I'd merge.

Yes, the evolution can be added afterwards. Branch rebased and commits squashed.

@haidubogdan thank you for your contribution. Merging.

Hi @Chris2011
I'm preparing an update for your observation :
aab0b8f

Unfortunately typescript doesn't have a classic language lexer, so it can't be used for a basic embedding.
From a first check pug eq to jade.
I will continue with sass, less, scss embedding. (I see that we don't have stylus yet), + an icon update.

@haidubogdan thx for your info. TypeScript is using the generic textmate grammar registration and LSP functionality. Just a hint. I dunno what needs to be done to also add textmate lexers as embeddings. Maybe the embedding provider needs to be changed but this is a whole different topic.