Issue with upgrade from 1.50.1 to 1.50.2
See original GitHub issueHi, just reporting that the latest version when msgpack was replaced with msgpackr, we now get this error when trying to run our project. We use the esm module (https://www.npmjs.com/package/esm) to load our project.
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: node_modules/msgpackr/dist/index.js
require() of ES modules is not supported.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:14 (9 by maintainers)
Top Results From Across the Web
What is the difference between new-sources and upload?
Description of problem: Is there a functional difference between new-sources and upload in rhpkg? Their descriptions sound very similar.
Read more >Dnf update just crashed my system - Ask Fedora
Hi, I just ran dnf update and Gnome froze entirely. Switching to a TTY with top I saw that gnome-shell and systemd-journal both...
Read more >Upgrading to VIOS 3.1 - IBM
The problem is that the newer VIOS 2.2.6.41 has some package versions higher than the older 3.1.0.10. My rule-of-thumb is: Always upgrade ......
Read more >How to upgrade the firmware on CK3X/R series using an SD ...
CK3X- question about firmware update and scanning barcodes ... software update improves performance of the device by addressing issues found ...
Read more >ec2-1.50.2 doesn't work with SSH <7.5 - Jenkins Jira
We also hit the issues after upgrading the plugin on ci.jenkins.io which currently uses the plugin to provision agents in AWS.
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

Well, it was not supposed to be a breaking change, in fact before this was merged we got the maintainer of msgpackr to release a change that allowed msgpackr to support node 10 as well. Maybe somebody that knows better can give us a hint on what changes to make in msgpackr so that this issue goes away.
The irony here is that msgpackr tries to be compatible with both pre node 12 (i.e. no es6 module support) and post 12, still the polyfill (ESM) that tries to solve this problem in a generic way fails when it shouldn’t do anything as it is already working!