fix: vite config types error #704
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
PatrykKuniczak
force-pushed
the
fix/error-of-vite-configs
branch
from
73e484d to
9d64a86
Compare
…me-extension` vite config types error
…on` and use it from `root` instead
PatrykKuniczak
force-pushed
the
fix/error-of-vite-configs
branch
from
9d64a86 to
c6126c6
Compare
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.
Priority*
Purpose of the PR*
I need to clean up my own mess :)
There's need to unify versions between packages, to have no errors on
vite.config.mtsofchrome-extensionpackageChanges*
I've unified versions of
rootandchrome-extensionpackage.jsonHow to check the feature
Run e.g
pnpm lint, and check it runs