-
Notifications
You must be signed in to change notification settings - Fork 71
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
WARNING in ./node_modules/react-google-drive-picker/dist/useInjectScript.js Module Warning (from ./node_modules/source-map-loader/dist/cjs.js): #32
Comments
I'm getting this error as well. |
Same, any updates? |
Same |
Add the following to your .env file GENERATE_SOURCEMAP= false |
@Jose-cd Can this be fixed? |
Add *GENERATE_SOURCEMAP=false *to your env file
…On Mon, Mar 13, 2023 at 2:33 AM Ricardo Ferreira ***@***.***> wrote:
@Jose-cd <https://github.com/Jose-cd> Can this be fixed?
—
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A36WYT3S7BMSS6N5H2NDZB3W33SWZANCNFSM54IP4WSQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Wouldn't that...suppress generation of source maps? I like source maps. I'll join the choir: @Jose-cd, we'd love a fix for this. |
I am also facing this same issue |
Any updates? Facing same issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Failed to parse source map from 'C:\Users\MYPC\Desktop\Projects\my-project\node_modules\react-google-drive-picker\src\useInjectScript.tsx' file: Error: ENOENT: no such file or directory, open 'C:\Users\MYPC\Desktop\Projects\my-project\node_modules\react-google-drive-picker\src\useInjectScript.tsx'
@ ./node_modules/react-google-drive-picker/dist/index.js 41:40-68
@ ./src/Pages/MyDrive.jsx 8:0-55 14:37-51 103:10-24
@ ./src/App.js 15:0-38 131:46-53
@ ./src/index.js 6:0-24 11:33-3
WARNING in src\Pages\MyDrive.jsx
Line 5:22: 'authResponse' is assigned a value but never used no-unused-vars
3 warnings have detailed information that is not shown.
Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.
The text was updated successfully, but these errors were encountered: