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.
BUG: ImportCall is an invalid AssignmentTargetType, should produce an Early ReferenceError
See original GitHub issueimport('') += 1;
Is producing a SyntaxError; however, like:
(() => 1) += 1;
It should produce an Early ReferenceError.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5
Top Results From Across the Web
Normative: Let all early errors be SyntaxErrors. by ... - GitHub
So the status is that JSC has yet to make these early errors at all implemented SyntaxError ... [JSC] Invalid AssignmentTargetType should be...
Read more >node.js - ReferenceError: Invalid left-hand side in assignment ...
You are declaring a constant while importing. I recommend you should use. let gcs = require('@google-cloud/storage');.
Read more >Modern JavaScript – Imports, Exports, Let, Const, and ...
To export something as a named export, we have to declare it first. export 'hello'; // this will result in error export const...
Read more >import - JavaScript - MDN Web Docs - Mozilla
Name of the module object that will be used as a kind of namespace when referring to the imports. Must be a valid...
Read more >FAQs | NHSN - CDC
If it is determined that incorrect data have been reported to NHSN, add, edit and delete records in NHSN as necessary to make...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@infinnie I think the 1=2 case was fixed by this commit https://github.com/Microsoft/ChakraCore/commit/13847da1662c5b603e1ae1f5b1bf978f21ed7b54 I guess that’s not made it into the version of Edge you’re using yet.
Closing per prior comment as spec changed to match existing behaviour.