-
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add skip
option
#146
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Is there a reason you wouldn't want
node_modules
and.git
directories to always be skipped even whenskip
is defined? - The new option needs to be mentioned in the readme.
I was thinking of this api as a way to override the default behavior as is common in builder configurations like webpack. Sorry about readme, fixed |
| datasource | package | from | to | | ---------- | ------------------- | ----- | ----- | | npm | vite-tsconfig-paths | 5.0.1 | 5.1.0 | ## [v5.1.0](https://github.com/aleclarson/vite-tsconfig-paths/releases/tag/v5.1.0) - Add `skip` option for adding additional directories to be skipped when searching for tsconfig.json files ([#146](aleclarson/vite-tsconfig-paths#146)) - Fix path resolution on Windows when other Vite plugins neglect to normalize the `importer` path before calling `this.resolve` in their `resolveId` hooks ([#157](aleclarson/vite-tsconfig-paths#157)) - Allow both tsconfig.json and jsconfig.json in the same directory ([`4124b09`](aleclarson/vite-tsconfig-paths@4124b09))
| datasource | package | from | to | | ---------- | ------------------- | ----- | ----- | | npm | vite-tsconfig-paths | 5.0.1 | 5.1.0 | ## [v5.1.0](https://github.com/aleclarson/vite-tsconfig-paths/releases/tag/v5.1.0) - Add `skip` option for adding additional directories to be skipped when searching for tsconfig.json files ([#146](aleclarson/vite-tsconfig-paths#146)) - Fix path resolution on Windows when other Vite plugins neglect to normalize the `importer` path before calling `this.resolve` in their `resolveId` hooks ([#157](aleclarson/vite-tsconfig-paths#157)) - Allow both tsconfig.json and jsconfig.json in the same directory ([`4124b09`](aleclarson/vite-tsconfig-paths@4124b09))
In monorepos it usefull to exclude big parts of repository that not related to vite
Resolves #147