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

add source maps to pkg #867

Closed
fffan64 opened this issue Sep 20, 2022 · 3 comments
Closed

add source maps to pkg #867

fffan64 opened this issue Sep 20, 2022 · 3 comments

Comments

@fffan64
Copy link

fffan64 commented Sep 20, 2022

Issue and Steps to Reproduce

when using react script > 5 and starting react local dev server, following warnings occurs:

[dev:react        ] Starting the development server...
[dev:react        ] 
[dev:react        ] Compiled with warnings.
[dev:react        ] 
[dev:react        ] Failed to parse source map from '/Users/jonathan.vacherat/Documents/CODING/nodejs/agpo-cloud-web/node_modules/@axa-fr/react-oidc/src/oidc/FetchToken.tsx' file: Error: ENOENT: no such file or directory, open '/Users/jonathan.vacherat/Documents/CODING/nodejs/agpo-cloud-web/node_modules/@axa-fr/react-oidc/src/oidc/FetchToken.tsx'
[dev:react        ] 
[dev:react        ] Failed to parse source map from '/Users/jonathan.vacherat/Documents/CODING/nodejs/agpo-cloud-web/node_modules/@axa-fr/react-oidc/src/oidc/OidcProvider.tsx' file: Error: ENOENT: no such file or directory, open '/Users/jonathan.vacherat/Documents/CODING/nodejs/agpo-cloud-web/node_modules/@axa-fr/react-oidc/src/oidc/OidcProvider.tsx'

and so with all files of the pkg

it seems the source are not included in pkg so loading of source map fails.

Versions

latest

Screenshots

Expected

No warning and proper debug with source maps

Actual

Warnings, cant debug non minified code

Additional Details

similar issue on random other pkg online : mebjas/html5-qrcode#396

@guillaume-chervet
Copy link
Contributor

I think the last version fixed it @fffan64 . Thank you again for your issue.

@fffan64
Copy link
Author

fffan64 commented Sep 22, 2022

i'm using an old version of react-script, v 4.0.3
the issue is still there but i believe if using 5.0.1 it will be resolved.

if it works for you with latest react-script, then it is ok, you can mark as closed, thanks !

@guillaume-chervet
Copy link
Contributor

Thank you @fffan64

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

2 participants