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

Cannot find module '@ai-sdk/amazon-bedrock' #1044

Closed
concaption opened this issue Jan 8, 2025 · 2 comments
Closed

Cannot find module '@ai-sdk/amazon-bedrock' #1044

concaption opened this issue Jan 8, 2025 · 2 comments

Comments

@concaption
Copy link

Describe the bug

Cannot find module '@ai-sdk/amazon-bedrock' imported from '/app/app/lib/modules/llm/providers/amazon-bedrock.ts'
at nodeImport (file:///app/node_modules/.pnpm/vite@5.4.11_@types[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:53047:19)
at ssrImport (file:///app/node_modules/.pnpm/vite@5.4.11_@types[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:52914:22)
at eval (/app/app/lib/modules/llm/providers/amazon-bedrock.ts:7:37)
at instantiateModule (file:///app/node_modules/.pnpm/vite@5.4.11_@types[email protected][email protected]/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:52972:5
Click outside, press Esc key, or fix the code to dismiss.
You can also disable this overlay by setting server.hmr.overlay to false in vite.config.ts.

Link to the Bolt URL that caused the error

http://localhost:5173/

Steps to reproduce

Current Version Tag: v"0.0.5" app-dev-1 | 📍 Current Commit Version: "4fd5040"

Expected behavior

Home page

Screen Recording / Screenshot

image

Platform

  • OS: [e.g. macOS, Windows, Linux]
  • Browser: [e.g. Chrome, Safari, Firefox]
  • Version: [e.g. 91.1]

Provider Used

No response

Model Used

No response

Additional context

No response

@concaption concaption reopened this Jan 8, 2025
@erambour
Copy link

erambour commented Jan 9, 2025

I had the same issue, so I've cleared existing containers & images, and re-build & -launched all
now it works

@thecodacus
Copy link
Collaborator

if you are using latest code and pulling the changes you need to update the dependencies or rebuild the container if using docker. latest code may add new dependencies to implement new feature

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

No branches or pull requests

3 participants