I propose that the NativeScript framework debugging experience is extended to match the featureset of web debuggers. This means support for the following:
in 1.3 release
in 1.6 release
in 1.7 release
I believe that work towards this goal will not only improve the debugging experience of NativeScript apps a great deal, but it would also make it easy for developers used to web debuggers to reuse their skills.
👍 This will also make NativeScript a better competitor for React-Native who have nailed the dev tools integration already.
Hey NativeScript Team! Can you develop a NativeScript Playground similar to the React Native Playground? Please check it out at RNPLAY.ORG.
I hope you can to this soon guys!
Hey @FlipOneDev that is a pretty good idea. Thanks for sharing it with us. You can imagine we can do something similar in our dojo 😄
Improving the debugging experience for NativeScript is SUPER critical. Hopefully there will be a better story sooner than later. It's very hard to adopt/learn a new framework while relying on "console.log" statements. Many higher level capabilities in NativeScript are almost pointless until there is a better core debugging story.
Eagerly waiting to see what milestone this gets assigned to. :)
@toddanglin We are actively working on it with high priority! With the 1.2 release (coming in two weeks) we will check the first task from the list - the JS profiler.
@PanayotCankov @KristinaKoeva lets write spec for each item from the tasks and create a new issue with more details.
This says it's in the 1.3 release... any details on it?
Our 1.3 release included the following improvements over the debugging experience.
For more information please take a look at our release notes
We are actively working on the rest of the App Inspector story so stay tuned.
Any notable improvements made on this issue for the 1.5 release? Is Visual Tree debugging still planned for 1.6?
Is the Nativescript inspector alive at all?
Hello, any update on this task ? It's a must have to be able to debug views, especially when using Nativescript with Angular.
@sjarrin +1 same here
any news on this?
During 2.4 we were working on parity with Android, see NativeScript/android-runtime#563.
For 2.5 we will continue working on this tooling with highest priority and will start enabling the tabs in the Chrome DevTools.
If you have any particular feedback please let me know. The goal is to enable Chrome Devtools to work in the same way in NativeScript as they work for web.