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.

Sign up for GitHub

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

Jump to bottom

SourceMaps in webpack for other projects #250

Closed
3 of 19 tasks
sasha240100 opened this issue Jun 16, 2017 · 1 comment
Closed
3 of 19 tasks

SourceMaps in webpack for other projects #250

sasha240100 opened this issue Jun 16, 2017 · 1 comment

Comments

@sasha240100
Copy link
Member

sasha240100 commented Jun 16, 2017 •
edited
Loading

Would be nice to have it. But I'm not confident of implementation yet. The ONLY way to have sourcemaps now is to compile whs on project side and it is a real disadvantage.

That's what you should do to HAVE sourcemaps of whs:

  1. Use whs/src/index instead of whs (which directs to whs/build/whitestorm.js. Already compiled one)
  2. Add this list of babel plugins to make whs be compiled as it is written in es2015+.
  3. Remove whs from /node_modules/ exlusion in babel-loader.
    As here:
    image

All this is very complicated now. And I think we should make things much simpler. I have no idea how to solve it right now. Any ideas?

Version:
  • v2.x.x
  • v1.x.x
Issue type:
  • Bug
  • Proposal/Enhancement
  • Question
  • Discussion
Tested on:
Desktop
  • Chrome
  • Chrome Canary
  • Chrome dev-channel
  • Firefox
  • Opera
  • Microsoft IE
  • Microsoft Edge
Android
  • Chrome
  • Firefox
  • Opera
IOS
  • Chrome
  • Firefox
  • Opera
@sasha240100
Copy link
Member Author

Fixed in #259

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sasha240100