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

chore: properly check for debug mode for node-gyp loglevel #689

Closed
wants to merge 1 commit into from

Conversation

mmaietta
Copy link
Contributor

@mmaietta mmaietta commented May 9, 2021

Updating logic to not rely on DEBUG env var, but instead use the debug module to check if electron-rebuild is enabled
Ref: #594

@codecov-commenter
Copy link

codecov-commenter commented May 9, 2021

Codecov Report

Merging #689 (9373ede) into master (ae73432) will increase coverage by 0.81%.
The diff coverage is 0.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #689      +/-   ##
==========================================
+ Coverage   68.69%   69.51%   +0.81%     
==========================================
  Files          11       11              
  Lines         575      574       -1     
  Branches      118      118              
==========================================
+ Hits          395      399       +4     
+ Misses        139      134       -5     
  Partials       41       41              
Impacted Files Coverage Δ
src/module-rebuilder.ts 84.00% <0.00%> (+0.55%) ⬆️
src/clang-fetcher.ts 81.42% <0.00%> (+5.71%) ⬆️

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 ae73432...9373ede. Read the comment docs.

@mmaietta mmaietta changed the title misc: properly check for debug mode for node-gyp loglevel chore: properly check for debug mode for node-gyp loglevel May 16, 2021
Updating logic to not rely on DEBUG env var, but instead use the debug module to check if electron-rebuild is enabled
electron#594
@electron-bot
Copy link

🎉 This issue has been resolved in version 3.2.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

3 participants