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

Source map all the things #2943

Merged
merged 7 commits into from
May 21, 2017
Merged

Source map all the things #2943

merged 7 commits into from
May 21, 2017

Conversation

fskreuz
Copy link
Contributor

@fskreuz fskreuz commented Apr 23, 2017

Description of the pull request:

Configure source maps to map all the way back to the source for both library and tests.

The only real hurdle was the module-skipping code. It needed to return a source map for the replacement code in order for the mapping to be a through and through.

TODO:

  • Source maps for tests
  • Source maps for src.
  • Make the source map not print gobble paths
  • Make the tests not print gobble paths

Fixes the following issues:

Annoying debugging of code using the bundled version as reference.

Is breaking:

No, i think.

Reviewers:

Everyone

Dependencies

Requires #2912 to go in first. It depends on several gobblefile changes there.

Copy link
Contributor

@evs-chris evs-chris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fskreuz fskreuz changed the title Source map all the things WIP: Source map all the things Apr 26, 2017
@fskreuz fskreuz changed the title WIP: Source map all the things Source map all the things May 20, 2017
@fskreuz fskreuz merged commit 202514e into ractivejs:dev May 21, 2017
@fskreuz
Copy link
Contributor Author

fskreuz commented May 21, 2017

Source maps should now go all the way back to source. Hopefully this helps in debugging. 👍

@fskreuz fskreuz deleted the source-map-all-the-things branch May 21, 2017 05:50
@evs-chris
Copy link
Contributor

Does this cause gobble to loop around the hardlink step for anyone else? I haven't gotten too far into it, but it looks like maybe creating a hard link in linux also triggers an fsevent on the file?

@fskreuz
Copy link
Contributor Author

fskreuz commented May 23, 2017

Looks like I missed checking the watch. PR inbound.

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.

2 participants