You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @dadaguai-git, thanks for creating this issue. @aws-amplify/[email protected] is compatible with [email protected]. Look inside node_modules/@aws-amplify/core/package.json to check which version of aws-amplify is being used. If it's not 6.0.13, try deleting the node_modules folder and running npm install again. Let me know if this works!
Hi @dadaguai-git, thanks for creating this issue. @aws-amplify/[email protected] is compatible with [email protected]. Look inside node_modules/@aws-amplify/core/package.json to check which version of aws-amplify is being used. If it's not 6.0.13, try deleting the node_modules folder and running npm install again. Let me know if this works!
Not really, but I found that I was able to run the app properly after installing it using pnpm
Before creating a new issue, please confirm:
On which framework/platform are you having an issue?
Vue
Which UI component?
Other
How is your app built?
vite
What browsers are you seeing the problem on?
Chrome
Which region are you seeing the problem in?
local
Please describe your bug.
@aws-amplify/ui-vue
version:4.1.0aws-amplify
version:6.0.13node_modules/@aws-amplify/ui-vue/dist/index.js:4:105
Could not resolve "@aws-amplify/core/internals/utils"
import { AuthAction, Category, InAppMessagingAction, GeoAction, StorageAction, setCustomUserAgent } from "@aws-amplify/core/internals/utils";
I checked the source code and found that there is really no such file directory, how to solve the problem?
What's the expected behaviour?
Being able to fetch this file and run the application successfully
Help us reproduce the bug!
Upgrade aws-amplify version and aws-amplify/ui-vue version to the latest version
Code Snippet
// Put your code below this line.
Console log output
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: