Resources:
Before submitting an issue, please consult our docs.
Stencil version: (run npm list @stencil/core from a terminal/cmd prompt and paste output below):
@stencil/[email protected]
└── @stencil/[email protected]
I'm submitting a ... (check one with "x")
[ ] bug report
[X] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or https://stencil-worldwide.slack.com
Current behavior:
_After running npm start, components are compiled and serve by the devServer, but there are no source map files._
Expected behavior:
_for debugging purpose it would be very helpfull to have source map, to map JS code to TS code_
Other information:
I have opened a thead in slack asking for this feature
--> https://stencil-worldwide.slack.com/archives/C79EANFL7/p1506398086000124
luchopcerra
All 17 comments
Hello! We are planning to add source maps soon once we have Stencil itself more stable and feature complete.
jgw96
on 9 Oct 2017
thanks! thats great news.
luchopcerra
on 9 Oct 2017
+1
iano123
on 27 Nov 2017
yes.. important feature for debugging purpose.
How do others debug Stencil app? Just wondering. I am writing console.log which is taking a lot of effort.
Does chrome debugger extension work for any one? I could not get that to work.
michaelchu28
on 11 Dec 2017
Since this issue, JS output is simply es2015 which makes it easy to understand how typescript transpiled it. We'll look to add source maps in the future, but for now going to close to keep issues organized, thanks.
adamdbradley
on 14 Feb 2018
It depends if you use jsx or not no?
iano123
on 14 Feb 2018
Do not quite understand why an unresolved issue is closed. Wonder how many of those are in the code base.
iano123
on 15 Feb 2018
@adamdbradley has there been any further progress on this front?
Not having source map support makes it impossible to do debugging using editor integrations, so development requires jumping back and forth between Dev Tools and (in my case) VS Code.
I think it's probably worth re-opening this issue now?
bitjson
on 15 Jun 2018
Same for me!
reicharm
on 26 Jun 2018
Why is this closed? This issue has not been addressed.
After minification reading component source in the debugger is still difficult, even though the typescript to es2015 step may be easy to understand.
apillard
on 24 Jul 2018
I recommend yall post in the Stencil slack https://stencil-worldwide.herokuapp.com/
arjunyel
on 31 Jul 2018
Can this be reopened? Would be really useful.
Alonski
on 22 Mar 2019
This is 2019 , 2 years after this issue was opened and still no source maps??? why???
liron-navon
on 29 Apr 2019
it's a big missing for a great piece of software like Stencil!
please add Sourcemaps
gino8080
on 6 May 2019
@manucorporat as of Stencil One, I think source maps are substantial...
kraftwer1
on 13 Jun 2019
It's September 2019, any news on this front?
ToothpickFactory
on 12 Sep 2019
@ToothpickFactory its on the roadmap https://github.com/ionic-team/stencil/issues/1744#issuecomment-526688386
arjunyel
on 12 Sep 2019
Related issues
rajiramamoorthi
·
3Comments
ryanmunger
·
3Comments
cjorasch
·
3Comments
glemiere
·
3Comments
lcswillems
·
3Comments
Most helpful comment
Can this be reopened? Would be really useful.