New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enable discussions for dumb questions like this #51
Comments
A local package export is an export from the package you are building. Some people avoid using relative imports by doing Node will look for that export in the The work around is then to symlink your package to a It will not automatically be published as npm will expect that installing your package will re-create the At the very end of the readme there's a Local Package Exports section with a @isaacs I also found the term "local" confusing at first. Maybe it is better to call it "current package exports" or "Importing package.json exports" ? I don't know 🤷🏻♂️ |
Isn't that what subpath imports are for? Anyway... I think this might be easier to pick up on if that TL;DR a) was first and b) was not collapsed by default. I do wonder how prevalent this setup is, and if |
I think technically the tl;dr isn't the bit that's collapsed, the tl;dr is the bit you see, and the longer explanation is the bit that's collapsed. I've seen them referred to as "local package exports" in discussions, but the node docs calls it "self-referencing a package by its name". |
I added
selfLink: false
to mytshy
config because I sawnode_modules
in mydist
folder and started to worry it'd be published. But--just now--I realized thatnpm
probably would avoid packing that folder unless explicitly instructed to (is that right?)....but I'm still fuzzy on what
selfLink: false
implies. What's a local package export? The top search result for this phrase is this site.The text was updated successfully, but these errors were encountered: