Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

debug version range can be wider

See original GitHub issue

Specifying ^3.0.0 may lead to unnecessarily duplicate debug packages since not every package needs to be compatible with node v4 which is no longer supported.

I think >=3.0.0 or something like this may be much better.

Issue Analytics

State:
Created 4 years ago
Comments:5

Top GitHub Comments

2reactions

RubenVerborghcommented, May 22, 2020

That’s a good point actually.

1reaction

RubenVerborghcommented, Jun 16, 2020

I turned debug into a peer dependency, so you are now able to use any version you want starting follow-redirects@1.12.0 (currently building).

Top Results From Across the Web

c# - Performance differences between debug and release builds

My experience has been that medium sized or larger applications are noticeably more responsive in a Release build. · One thing that can...

2x-3x Performance Improvements for Debug Builds

We noticed 2x – 3x improvements in all the projects we tried. More STL-heavy projects may see larger improvements.

Configure on-device developer options - Android Developers

Enable developer options and USB debugging · Android 9 (API level 28) and higher: Settings > About Phone > Build Number · Android...

Setting debug preferences - IBM

Debug Daemon preferences Ranges and combinations of ports can be specified in comma-separated lists, hyphenated ranges, or a combination of the two. By...

Testing a release build | Apple Developer Documentation

The debugger can attach to a development-signed release build, but be aware that it ... Because of the wide the range of variation...