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

How to generate source maps for debugging in VS Code? #1103

Closed
aschrijver opened this issue Jul 11, 2017 · 2 comments
Closed

How to generate source maps for debugging in VS Code? #1103

aschrijver opened this issue Jul 11, 2017 · 2 comments

Comments

@aschrijver
Copy link
Contributor

Hi,

On a new ignite project, how do I get source maps to be generated? Need it for debugging in VS Code and setting breakpoints, etc. The .babelrc has "sourceMaps": true added, no other changes.

I am on:

System
  platform           linux                                                                                                
  arch               x64                                                                                                  
  cpu                4 cores                                          Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz  
  directory          /home/arnold/Development/fullcircle/Fullcircle                                                       

JavaScript
  node               8.1.2        /usr/local/bin/node  
  npm                4.6.1        /usr/local/bin/npm   
  yarn               0.24.6       /usr/bin/yarn        

React Native
  react-native-cli   2.0.1       
  app rn version     0.45.1      

Ignite
  ignite             2.0.0        /usr/local/bin/ignite  

Android
  java               1.8.0_111    /usr/bin/java  
  android home       -            undefined
@aschrijver
Copy link
Contributor Author

Well, the issue appears to be with Visual Studio Code. Apart from #1083 ignite is working fine, though this last one is a blocker for ES6 tests and testing UI. Luckily, I can postpone that problem to some future date. Setting up JS/RN stacks is a huge PITA, but at least Ignite helped a bit. Thanks.

@jamonholmgren
Copy link
Member

@aschrijver glad Ignite helped a little, and I concur that JS/RN can be a major PITA sometimes.

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