🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

More infromation: https://github.com/oxc-project/oxc#%EF%B8%8F-performance

For more detailed and specific linting users may opt of eslint

Hi,

It's Kenneth from VS Code. I'm reaching out to tell you that we plan to feature your awesome VS Code extension pack on our marketplace https://marketplace.visualstudio.com/#VSCode in the next iteration.

Please work with your community to resolve any major issues, as you'll probably see a significant bump in new users trying your extension.

Thanks for the great work, and happy coding!

/k

Kenneth Auchenberg
Visual Studio Code
Program Manager, Microsoft

Cool. If you have more suggestions go ahead.
I am planning to update and publish new version. Since tooling has improved a lot since last version.
Originally posted by @mubaidr in #14 (comment)

As requested for suggestions, I decided to open an issue to discuss options and allow others to contribute.

The pack already includes:

Vue 3 Snippets - A Vue.js 3 And Vue.js 2 Code Snippets Extension
by @hollowtree

But this extension hasn't been updated in 2 years, and the repo still says "Vue 2" even though the Marketplace lists "Vue 3".

There's a similar extension with ~1.5m installs:

Vue VSCode Snippets - Snippets that will supercharge your Vue workflow
by @sdras

This one is more recently updated and may be more actively maintained.
I'm unsure if the pack should prefer one over the other, but I wanted to highlight a possible alternative.

I noticed that the extension which is already in the pack:

TypeScript Vue Plugin (Volar)
by @johnsoncodehk

says:

It's recommended to use take over mode instead of this plugin.

Although that looks like a deprecation warning, it means to disable the native TS language server in VS Code while using the extension, which allows the Volar language server to "take over" handling regular TS files and Vue SFC files with TS.
The instruction is more clearly stated on the Official Vue Page
The configuration change is significant. Otherwise, two language servers are parsing TS, which impacts performance.
Maybe the extension pack should call attention to the instructions since the extension cannot automate the change.

Since the update will be forward-looking, maybe the extension pack should include Official Vite and Vitest extensions:

Vite - VS Code for Vite
by @antfu

Vitest - Run and debug Vitest test cases
by @zxch3n

It would be great to also bundle npm-scripts with this, as that makes building and serving due projects even easier.

https://github.com/Duroktar/vscode-npm-scripts

Instructions are: Update eslint config (.eslintrc.js or .eslintrc.json):

There several such files on my PC. Which one do I update?

I've been working with this extention which is already by itself pretty cool and am really thankful for it!!!

Would really like to know if it is planed to add such functiuonality, would also like to help :)

Hi, I used recommended settings to get started . But then most js issues are ignored in vue files. What do I miss? Here is my eslint.js file. Thanks in advance

module.exports = {
  root: true,
  env: {
    browser: true,
    commonjs: true,
    es6: true,
    node: true
  },
  extends: [
    "standard",
    "eslint:recommended",
    "plugin:vue/recommended"
  ],
  parserOptions: {
    "parser": "babel-eslint",
    "ecmaFeatures": {
      "jsx": true
    },
    "sourceType": "module"
  },
  // required to lint *.vue files
  plugins: [
    'vue'
  ],
  // add your custom rules here
  rules: {},
  globals: {}
}

• vscode-eslint
• vscode-prettier
• recommend vs code settings
• recommended eslintrc.json
• recommended .editorconfig
• Research if its possible for an extension to update user settings.

I will add recommend and common settings for this extension pack to further enhance the development experience and setup tools like eslint.