mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
8550412bb0eaa3b80ae8725f3bed128d629b9d61
meteor debug using the Node 8 inspector.
This is the feature that excites me most about Meteor 1.6, hands down. Benefits include: * Works with `meteor test[-packages] --debug-port 9229` (for tests), as well as just `meteor debug` (for apps). * The application process waits patiently for the debugger to attach, so you don't have to race to open the debugger. * The application process pauses at a location just after all server code has been evaluated, but before any code starts executing, giving you a chance to set reliable breakpoints anywhere in server code. This is much better than using the `node --inspect-brk` flag, since that stops too soon to set any useful breakpoints. * The application server runs at full speed, so you don't have to wait forever to hit that all-important breakpoint, and you don't lose nearly as much time if you accidentally continue past the line of code where the trouble is occurring. * Even if your application is stuck in an infinite loop, you can still attach the debugger, pause execution, and debug the loop. * No more `node-inspector`! Instead, you can now debug your server code in native Chrome DevTools, or several other high-quality inspector clients, such as VS Code or WebStorm (seriously, check out the documentation: https://nodejs.org/en/docs/inspector/#inspector-tools-clients). The list of debuggable processes can be found at the URL chrome://inspect. * Realistic performance and memory profiling is now possible via the familiar DevTools interface. * I highly recommend this Chrome extension that automatically (re)connects to any open inspector sockets, so you don't have to keep manually (re)attaching the debugger: http://june07.com/nim * The implementation of `meteor debug` no longer has to proxy multiple private/public debugger ports. Look at all that deleted code! This new inspector is so much better than the old `node-inspector` that I've been using the release-1.6 branch to debug problems in Meteor 1.5, despite the risks of using Node 8, because those risks are so far outweighed by the quality of the new debugging experience. That said, the experience isn't perfect (yet). I welcome your feedback on the Meteor 1.6 PR: https://github.com/meteor/meteor/pull/8728
Meteor is an ultra-simple environment for building modern web applications.
With Meteor you write apps:
- in pure JavaScript
- that send data over the wire, rather than HTML
- using your choice of popular open-source libraries
Try the getting started tutorial.
Next, read the guide or the reference documentation at http://docs.meteor.com/.
Quick Start
On Windows, the installer can be found at https://www.meteor.com/install.
On Linux/macOS, use this line:
curl https://install.meteor.com/ | sh
Create a project:
meteor create try-meteor
Run it:
cd try-meteor
meteor
Developer Resources
Building an application with Meteor?
- Announcement list: sign up at http://www.meteor.com/
- Having problems? Ask for help at: http://stackoverflow.com/questions/tagged/meteor
- Discussion forums: https://forums.meteor.com/
Interested in helping or contributing to Meteor? These resources will help:
We are hiring! Visit meteor.io/jobs to learn more about working full-time on the Meteor project.
Uninstalling Meteor
Aside from a short launcher shell script, Meteor installs itself inside your home directory. To uninstall Meteor, run:
rm -rf ~/.meteor/
sudo rm /usr/local/bin/meteor
On Windows, just run the uninstaller from your Control Panel.
Languages
JavaScript
91.1%
TypeScript
3.9%
Shell
0.9%
Java
0.7%
Swift
0.7%
Other
2.5%
