Skip to content

Releases: microsoft/vscode-react-native

0.3.0

13 Feb 17:47
Compare
Choose a tag to compare

0.3.0

  • Updated to use node2 debug engine instead of node. We now spawn a separate node process to run the app logic rather than using node's vm infrastructure.
  • Fixed support for android variants
  • Fixed the ability to open source files by tapping on stack frames when the app red-boxes

Release 0.2.4

08 Dec 21:13
Compare
Choose a tag to compare
  • Allowed using this extension in a workspace with the react-native project in a subfolder.
  • Ignore references to inline sourcemaps, in the hopes of finding another refernece to a map file
  • Exposed react-native-tools.showInternalLogs and react-native-tools.logLevel to print additional output for debugging issues with the extension.
  • Added CHANGELOG.md

Release v0.2.0

16 Sep 17:56
Compare
Choose a tag to compare
  • Added support for running and debugging with Exponent. See the readme for more details
  • Added a "Restart packager" command to stop and re-start the packager, additionally clearing the packager's cache.

Release v0.1.6

29 Aug 20:59
Compare
Choose a tag to compare
  • Fixed an issue with execute permissions and navigating to a stack trace
  • Fixed a typo in package.json relating to what file types support debugging
  • Fixed an issue where the output window would always open whenever you open a folder with a package.json
  • Added support for --variants with android projects in launch.json
  • Added support for iOS projects using xcworkspaces rather than xcodeproj files
  • Added support for debugging typescript / using sourcemaps; thanks a lot @frogcjn for work on this feature!
  • Refactored most of our debugging code out of the process being debugged so less should show up in stack traces
  • We now determine whether a project is a react-native project by asking react-native, rather than using our own approach.

Release v0.1.5

13 Jun 20:51
Compare
Choose a tag to compare

This release includes the following changes:

  • If you have two projects open at the same time, if you configure the settings.json to provide a port for the react native packager, you should be able to debug both projects at the same time.
  • When you have an error on your react native application and you are running it on a simulator, react native shows a red screen with a stack trace. VSCode is now supported as an editor so if you click on a given filename it should open in the correct line number in your instance of VSCode.
  • We added support for mocking native functionality.
  • Bug fixes.

Special thanks to @mroswald and @chrbala for their contributions to the code base.

Release v0.1.4

12 Apr 20:02
Compare
Choose a tag to compare

This release fixes some issues relating to launching on iOS devices.

Release v0.1.3

06 Apr 22:12
Compare
Choose a tag to compare
  • Updated our telemetry library so that we can better understand the usage of this extension.
  • Updated some of our error messages so that they're more helpful.
  • Fixed an issue caused by the renaming of the node debugging extension in VS Code 10.12.
  • Various internal changes to help with testing the extension.

Release v0.1.2

14 Mar 18:37
Compare
Choose a tag to compare

Remove references to "Preview"

Release v0.1.1

14 Mar 17:07
Compare
Choose a tag to compare

This release includes the following changes:
• React Native 0.21 and 0.22 are now supported.
• Several improvements to how we detect and report errors. Errors are now more visible in the debug output, previously some error messages were not fully propagated to the user.
• We now show a status bar in VS Code when the packager is started or stopped by our extension.
• Improved the way we sandbox the React-Native app logic which solves an issue where the alert function stopped working in live reload scenarios.
• Updated IntelliSense support to use VS Code's internal Salsa support (VS Code versions 0.10.10+ ).
• React Native: Run Android command will launch the app in all available Android devices. Debugging logic will chose a single Android device when multiple are available. A specific target can be set by setting the device id to use (from adb devices) in the target setting in the launch.json.
• We show the LogCat output in a Channel Output - custom LogCat arguments can be set in the logCatArguments setting in launch.json.
• Added support for using the extension in Windows 7, Windows 8.1 and Windows 10 as well as minor fixes related to Mac OS.
• We don't overwrite allowJs settings in the tsconfig.json file if it's already set.

Release v0.1.0 (Preview)

20 Feb 01:34
Compare
Choose a tag to compare

Added Command palette, IntelliSense and Debugging support for React Native projects