feat: treat vite config files as dev files #130
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
guym4c
approved these changes
Nov 13, 2024
zacowan
approved these changes
Nov 13, 2024
oneamexbot
added a commit
that referenced
this pull request
Nov 15, 2024
# [16.3.0](v16.2.0...v16.3.0) (2024-11-15) ### Features * treat vite config files as dev files ([#130](#130)) ([ef8c6ab](ef8c6ab))
|
🎉 This PR is included in version 16.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Marks the vite / vitest config files as development files so that the
import/no-extraneous-dependenciesrule works properly.Motivation and Context
Without this, eslint throws an error saying any imports they use should be added to dependencies not devDependencies.
How Has This Been Tested?
Packed and installed in a repo using vitest.
Types of changes