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

fix: no source maps in production #230

Merged
merged 1 commit into from
Apr 2, 2020
Merged

fix: no source maps in production #230

merged 1 commit into from
Apr 2, 2020

Conversation

mattp94
Copy link
Contributor

@mattp94 mattp94 commented Apr 1, 2020

Fixes #202

Description

Currently, source maps are generated in the production build but they point to source files that don't exist in the distribution.

Solution

I suggest to disable source maps generation during the production build.

@alex-cory
Copy link
Collaborator

alex-cory commented Apr 1, 2020

@mattp94 This is awesome! Thank you! Did you test this and it worked fine?

@mattp94
Copy link
Contributor Author

mattp94 commented Apr 2, 2020

@alex-cory Yes, I tested it and it worked well 🙂! If you're okay with that change, I'll create the same PR on https://github.com/alex-cory/use-ssr as we also have warnings coming from this package

@alex-cory
Copy link
Collaborator

Go for it! @mattp94

@alex-cory alex-cory merged commit dcdf51c into ava:master Apr 2, 2020
@mattp94 mattp94 deleted the fix-production-source-maps branch April 2, 2020 18:45
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

Successfully merging this pull request may close these issues.

Warnings about missing source map files when used in ParcelJS + TypeScript project
2 participants