vue-intellisense
vue-intellisense copied to clipboard
A CLI tool to help enabling IntelliSense on your Vue components
I've done the most basic setup and get this error when trying to run `vue-int --input /src/components/modal/test --output vetur --recursive` `Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /usr/local/lib/node_modules/vue-intellisense/cli.js...
@boydaihungst I have release ESM only build of vue-intellisense. 2 tests in `aliasParser.test` broke and wasn't able to fix them. can you have a look and help me fix them?...
The index.cjs.js file in dist folder uses `require('fs/promises')` instead of `require('fs').promises` causing "Error: Cannot find module 'fs/promises'".
I define vue Custom Directives like `v-permission`, and how to intellisense at every Html tag.
- [x] Add support jsconfig.json, tsconfig.json. [https://github.com/CyCraft/vue-intellisense/issues/17](https://github.com/CyCraft/vue-intellisense/issues/17) - [x] update alias guide. [https://github.com/CyCraft/vue-intellisense/issues/15](https://github.com/CyCraft/vue-intellisense/issues/15)
@boydaihungst is it possible to refactor the aliases setup to use `jsconfig.json` or `tsconfig.json` instead instead? Since this is probably what all developers already use to setup aliases.
Add small example on how an alias config file should be made
If I start writing `
First of all: Thank you for your work! It would be great to configure to generate configs only from vue-files. When exporting a component via a index.ts file the component...
based on tests here: https://github.com/sindresorhus/npm-name-cli Add similar tests for the CLI tool in `packages/vue-intellisense`