Update VitePluginUsage.vue

[hinogi]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Documentation
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes
• No

The PR fulfills these requirements:

• It's submitted to the dev branch (or v[X] branch)
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• It's been tested on a Cordova (iOS, Android) app
• It's been tested on an Electron app
• Any necessary documentation has been added or updated in the docs or explained in the PR's description.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to start a new feature discussion first and wait for approval before working on it)

Other information:

[yusufkandemir]

You didn't share the point of this PR. But, from what I can see it's a recommendation for a better organization. However, create-vite creates the style file in src/style.css. create-vue creates the style files in src/assets/.... Neither uses Sass as Vite recommends using modern CSS instead. This change would not align with either of the templates, so I will close this PR. Thanks for your time and understanding.

[hinogi]

The file ending was not the point, but if it is .sass it is not where the article shows it would be not is the name correct.

[yusufkandemir]

Not sure if I understand anything, but I will try my best. Sass was a side point I mentioned. They either place styles in src/ or src/assets, so creating it in src/css doesn't align with either of the templates.

[hinogi]

This was my point.

[hinogi]