Shared/remote configs from NPM packages

[banjo]

Description

It would be nice to be able to share configs based on NPM packages, so that we basically fetch the config from node_modules instead of from a git source.

What problem it is solving?

All of our git repositories are not publicly available. We cannot clone them without a lot of security setup first, which eliminates the opportunity for us to share configs with git.

We basically use npm to share all of our other common configs like linting, formatting, validation, and more via npm, so it would be nice if we could share this config for that as well.

[banjo]

Woah, it seems like I have been sleeping on the extends command, that is exactly what I was looking for.

Was a bit hard to find in the docs, would maybe be nice to include it in the examples section for easier access 🙏

Thanks for the great work!

[kamontat]

@banjo extends didn't support npm package in the ways that we usually see in npm based config.

For example you cannot use extends: ["@example/config"], you have to use extends: ["./node_modules/@example/config/src/default.json"] instead.

[banjo]

Yeah, I noticed that. Even though it works like it does now it would maybe look a bit more clean if you could import it directly from the package exports path.