Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: source code & test app debugger #685

Merged
merged 1 commit into from
Mar 17, 2017
Merged

feat: source code & test app debugger #685

merged 1 commit into from
Mar 17, 2017

Conversation

willviles
Copy link
Contributor

I've put together a very basic Lux development debugging utility, which significantly speeds up the process of debugging the Lux source code and test application.

To use, simply run npm run debugger from the root of the Lux repo.

The debugger does the following:

  1. Cleans the Lux environment => npm run clean
  2. Builds Lux source into /dist => npm run build
  3. Builds the test app => cd test/test-app && lux build
  4. Runs node inspector => node --inspect=4000 dist/boot.js
  5. Opens the URL in Chrome (Mac only) using an osascript (node opn doesn't respect chrome-devtools URLs)

@codecov
Copy link

codecov bot commented Mar 16, 2017

Codecov Report

Merging #685 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #685   +/-   ##
=======================================
  Coverage   92.38%   92.38%           
=======================================
  Files         180      180           
  Lines        1996     1996           
=======================================
  Hits         1844     1844           
  Misses        152      152

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7858af5...6c2a577. Read the comment docs.

Copy link
Contributor

@zacharygolba zacharygolba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏 Excellent work. This will be very useful!

package.json Outdated
"test": "nyc -i ./lib/babel-hook.js --instrument false --source-map false mocha --opts mocha.opts"
"test": "nyc -i ./lib/babel-hook.js --instrument false --source-map false mocha --opts mocha.opts",
"debugger": "node test/utils/debugger/dist/debug.js",
"debugger-build": "rollup -c test/utils/debugger/rollup.config.js"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is completely subjective and isn't a big deal so feel free to ignore this if you would like.

I'm thinking build:debugger may be a better name for the debugger build script. In a vacuum debugger-build and build:debugger seem pretty similar but imo, npm run build:debugger reads better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants