-
Notifications
You must be signed in to change notification settings - Fork 579
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
Error: 'request' is not exported by __vite-browser-external #2648
Comments
Related #2478 @subhendukundu in the related issue there is a PR to fix the same kind of problem, might be useful |
i solved it with the following resolve: {
alias: [
{
find: '@', replacement: path.resolve(__dirname, './src'),
},
{
find: './runtimeConfig', replacement: './runtimeConfig.browser',
}
]
} |
https://ui.docs.amplify.aws/getting-started/installation#vite A sub-product of amplify also suggests what @Fanna1119 is using above, although pared down:
Suitable workaround for me. |
Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Confirm by changing [ ] to [x] below to ensure that it's a bug:
Describe the bug
I am trying to use
@aws-sdk/client-sns
withesbuild
but won't build echoing an errorError: 'request' is not exported by __vite-browser-external
.I have tried to use this which doesnt fix the issue. https://github.com/aws-amplify/amplify-js/issues/7499#issuecomment-804386820
A reproducible example would be https://github.com/subhendukundu/worker-auth-providers/tree/discord/example
Are there any workarounds to fix it?
The text was updated successfully, but these errors were encountered: