This repository was archived by the owner on Sep 2, 2023. It is now read-only.
This repository was archived by the owner on Sep 2, 2023. It is now read-only.
Proposal: Support loading package by own "name" #306
Description
This has been discussed before, but I think it's a good time to consider it now.
A very common problem in Node.js applications is the backtracking problem where you have to always reference modules through ../../compo
612D
nents/name.js.
Since we're loading the package.json when checking the module boundary, we thus also know the package.json "name" that any given module is in.
What we could do is support loading a package by its own package.json "name" by default.
This would allow conventions where users just set a package.json name and can then use import "pkgname/components/name.js" instead.
It's a very small feature that seems like it could solve a pain point quite elegantly.
Would be nice to discuss this further at the next meeting.