Skip to content
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

Version conflicts after using aws-amplify/ui-vue and aws-amplify #4974

Closed
4 tasks done
tuskermanshu opened this issue Feb 1, 2024 · 3 comments
Closed
4 tasks done
Assignees
Labels
question General question

Comments

@tuskermanshu
Copy link

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.0
aws-amplify version:6.0.13
node_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

@github-actions github-actions bot added the pending-triage Issue is pending triage label Feb 1, 2024
@esauerbo esauerbo added question General question and removed pending-triage Issue is pending triage labels Feb 1, 2024
@esauerbo
Copy link
Contributor

esauerbo commented Feb 1, 2024

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!

@esauerbo esauerbo self-assigned this Feb 1, 2024
@tuskermanshu
Copy link
Author

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

demo_20240126174341

@esauerbo
Copy link
Contributor

esauerbo commented Feb 2, 2024

Glad to hear it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question General question
Projects
None yet
Development

No branches or pull requests

2 participants