Fix vuex create store import error #16
Merged
Conversation
This file contains hidden or 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
…upport Co-authored-by: ann.jacob <ann.jacob@aot-technologies.com>
|
Cursor Agent can help with this pull request. Just |
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.
Remove an incorrect Vuex type declaration and update frontend configuration to resolve
createStoretype errors and enable a clean build.The
Module '"vuex"' has no exported member 'createStore'error was caused by an ambient module declaration insrc/vite-env.d.tsoverriding the actual Vuex types. This PR removes that declaration and includes related fixes for TypeScript path aliases, missing dependencies (axios,@types/node), Vuex store registration, and Prettier formatting to ensure a successful production build.