Repository navigation
Re-add default export for v5 esm #770
Description
In v4 you could
import yaml from "js-yaml";
Now the default export from
https://github.com/nodeca/js-yaml/blob/v4/lib/index_vite_proxy.tmp.mjs#L37
is gone... and all our pipelines are failing.
SyntaxError: The requested module 'js-yaml' does not provide an export named 'default'
I read the v5 changelog and migration guide, but I feel neither addresses why this common pattern was dropped. I feel you coud still have a default export with the most broadly used functionality available.
Activity
puzrin commentedon Jun 24, 2026
I guess, you can do
import * as yaml from js-yaml. I'm not sure double exports are a good idea.Update migration info, close nodeca#770
rlindner81 commentedon Jun 24, 2026
The issue is not for code that I can change, it's one of our dependencies that does the importing... I do see your point regarding double exports.
A major version change is the best place for you to introduce this change from having a default export to having none. It would still be good to acknowledge it in the changelog/migration guide.
puzrin commentedon Jun 24, 2026
See 89024c4, already done. But I sit on the other side and may miss something about "how users see the situation". If you think the docs can be improved further, suggest a PR. Sorry for the friction, but that's an essential part of any big major release.