From caec801f6fee3fc1ffde333ba37eba0b8c5e1aa5 Mon Sep 17 00:00:00 2001 From: Matheus Castro Date: Sun, 24 Jul 2022 00:01:31 -0300 Subject: [PATCH] Add TOOL_NODE_FLAGS as a tip on the DEVELOPMENT.md file. This is already documented in the Environment Variables file, but it's a bit hidden. --- DEVELOPMENT.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index dbbdfefcdd..a34dd51841 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -43,13 +43,19 @@ can run Meteor directly from a Git checkout using these steps: $ /path/to/meteor-checkout/meteor run ``` - > _Tip:_ Consider making an easy-to-run alias for frequent use: + > _Tip 1:_ Consider making an easy-to-run alias for frequent use: > > alias mymeteor=/path/to-meteor-checkout/meteor > > This allows the use of `mymeteor` in place of `meteor`. To persist this > across shell logouts, simply add it to `~/.bashrc` or `.zshrc`. + > _Tip 2:_ When working with meteor tool, it may be helpful to use the debugger to check what's happening. You can do this using the following flag: + > + > TOOL_NODE_FLAGS="--inspect-brk" mymeteor + > + > Then you can use the chrome debugger inside `chrome://inspect`. + ### Notes when running from a checkout The following are some distinct differences you must pay attention to when running Meteor from a checkout: