Error with node 14.16.1
See original GitHub issueHave been successfully using Bytenode for a project on node 12. Switched to node 14.16.1, and getting the following error when trying to run module after compile with bytenode 1.2.3. Found same error in #35, so I also tried v1.1.2.
terminate called after throwing an instance of 'std::out_of_range' what(): vector::_M_range_check: __n (which is 0) >= this->size() (which is 0) Aborted
Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Comments:10
Top Results From Across the Web
when i tried to install node 14.16.0 or 14.16.1, i am getting ...
1, i am getting this error. pls help me fix this issue. #2558. Open.
Read more >Node 14.16.0: Error-Messages after Update
I've updated Node from version 12.x.x to 14.16.0. After this I get serveral error messages when I try to start the server.
Read more >Node v14.16.1 (LTS)
This is a vulnerability in the y18n npm module which may be exploited by prototype pollution. You can read more about it in ......
Read more >How to fix 'npm does not support Node.js v14' error on ...
My first attempt was updating over the top of my existing node.js installation. I then tried uninstalling node.js installation (Windows Add/ ...
Read more >Node JS 14.16.1
Version Downloads Last Updated Status
Node JS 19.3.0 4584 Wednesday, December 14, 2022 Waiting for Maintainer
Node JS 19.2.0 23071 Wednesday, November 30, 2022 Approved
Node...
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 FreeTop 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
Top GitHub Comments
@OsamaAbbas thank you so much for the offer, but the issue turned out to be on our end. While we were compiling with version 1.2.3 our project dependency was old & as such when we ran the compiled files we were getting the error. Updating the project dependency to match 1.2.3 we no longer get the error.
Thank you so much for creating & maintaining such a great project! This issue can be closed.
Thank you. Good luck.