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

Cherry-pick CSS Sourcemaps #2917

Merged
merged 3 commits into from Apr 12, 2019
Merged

Conversation

wbinnssmith
Copy link
Contributor

@wbinnssmith wbinnssmith commented Apr 11, 2019

This forward-ports @mischnic's work on css sourcemaps into the v2 branch.

Note that this is a cherry-pick of #2489 as well as two other commits necessary for existing tests to pass. The css integration tests continue to be skipped, and it's possible we're missing more code that we don't exercise yet. A full merge of master back into v2 should resolve that.

mischnic and others added 3 commits April 11, 2019 12:32
)

* Defer throwing asset errors until after dependencies are handled.

This allows compiled langauges like Elm that handle their own dependency
compilation to set up watchers for dependencies so that hot-reload
continues to work due to errors in new depdenencies. Fixes #2147.

* Fix Elm error generation.

I'm not entirely sure why this fix is necessary, but without it a
compile error during a rebuild results in Parcel printing "Unknown
error" instead of anything useful. Since we are intecepting the error
though, we can also remove redundant stack information.

* Add test for tracking dependencies on error

* revert hmr-runtime changes

* Transform all errors in Pipeline.process.

This prevents error data from being lost when Pipeline is run via
`WorkerFarm`.

* Separate error-depenency test input from basic Elm tests.

* Update ElmAsset.js
@DeMoorJasper
Copy link
Member

DeMoorJasper commented Apr 12, 2019

Perhaps it would be a better idea to try and merge master into v2 instead? (although this is getting pretty hard as there's a diff of a couple hundred commits)
I don't really see a reason to cherypick merge this instead as Sourcemaps in v2 should probably be less hacky.

@wbinnssmith
Copy link
Contributor Author

I don't really see a reason to cherypick merge this instead as Sourcemaps in v2 should probably be less hacky.

I mostly want the tests, but I suppose everything could just be copied over.

Merging master into v2 is a pretty big undertaking that I probably won't have much context on 😄 I'd definitely be on board with that but I'm not the best to do so.

@wbinnssmith wbinnssmith merged commit 9669544 into v2 Apr 12, 2019
@wbinnssmith wbinnssmith deleted the wbinnssmith/cherry-pick-css-sourcemaps branch May 9, 2019 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants