feat: custom eslint parser for Vue Vine

[ShenQingchuan]

Why this?

We can't reuse vue-eslint-parser because it's made for scanning and analyzing the .vue SFC file, and may not satisfies our requirements that well.

We must make our own custom ESTree to represent a VCF(Vine component function).

There'll be a representation of Vue's template in VCF's return statement.

Milestones

• Tokenize all items from vine tagged template string node, and adjust position based on global offset.
• Build VTemplateRoot ESTree root node.
• analyze used in template variables

May put in another PR

• Create eslint-plugin-vue-vine package to maintain rules for Vue Vine.

[netlify]

✅ Deploy Preview for vue-vine ready!

Name	Link
🔨 Latest commit	a5f880f
🔍 Latest deploy log	https://app.netlify.com/sites/vue-vine/deploys/655c8b4c4526aa00086bb53e
😎 Deploy Preview	https://deploy-preview-56--vue-vine.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[so1ve]

@ShenQingchuan I see there are many rollup boilerplate code in our repo. Shall we refactor them to make them reuseable, or use pkgroll instead? I use it to build the create-vine-app cli in #49

[ShenQingchuan]

@ShenQingchuan I see there are many rollup boilerplate code in our repo. Shall we refactor them to make them reuseable, or use pkgroll instead? I use it to build the create-vine-app cli in #49

@so1ve For sure! Any refactor that brings efficient is definitely worth it.

If we can't avoid do that for 2 times due to there're 2 PRs left here right now, we could just setup them in the same way, and decrease the difference as much as possible so that there'll not be so many conflicts to resolve.

If you chose to do that in one of these 2 PRs, you can go for it and rebase it in the other PR.

Thanks! 💖 You're my GOAT !

[so1ve]

I wonder if doing such refactor in these two PRs will cause huge merge conflict... Let's merge these two PRs anyway, thus we can refactor in main.

[ShenQingchuan]

Preview video

vue-vine-eslint-parser-with-desc.mp4

Drawbacks now

Based on what's been tested so far, there are some standard rules that still need to be handled specifically for the Vue Vine scenario.

For example, StartTag for an HTML tag that taking up multiple lines and having different attributes in rows can cause ESLint to report no-multi-spaces. eslint-plugin-vue redefines a no-multi-spaces rule with the same name to cover them.

Which means we may need to do the same.

[baiwusanyu-c]

[so1ve]

[Simon-He95]

[DaZuiZui]