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.

new.target use causes errors in Node v4.

See original GitHub issue

I’m not sure what versions of Node are supported but noticed Node v4 erroring because of new.target use.

Issue Analytics

State:
Created 6 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

2reactions

jdaltoncommented, Sep 17, 2017

@TimothyGu Ah, should probably be called out in the readme. I was looking for an engines field or something but couldn’t come up with anything.

0reactions

adipascucommented, Jun 26, 2018

This also crashes when using Fetch As Google. Usage of ES6 features in published npm packages should be documented. There is currently an unwritten rule to only publish ES5 code.

Top Results From Across the Web

15 Common Error Codes in Node.js and How to Fix Them

15 Common Error Codes in Node.js and How to Fix Them · 1. ECONNRESET · 2. ENOTFOUND · 3. ETIMEDOUT · 4. ECONNREFUSED...

Best Practices for Node.js Error-handling - Toptal

Using Node.js built-in Error object is a good practice because it includes intuitive and clear information about errors like StackTrace, which most developers ......

A Comprehensive Guide To Error Handling In Node.js

Errors happen in every application. Devs have to decide: do you write code to handle the error? Suppress it? Notify the user?

Move from instanceof to new.target check in all function-based ...

Since Node.js uses V8 like Chromium, !new.target should be the correct ... I'm sure it will cause breakage for some, but the performance ......

Errors | Node.js v19.3.0 Documentation

If present, the error.cause property is the underlying cause of the Error . It is used when catching an error and throwing a...