shareable config from an npm package

if this is already supported, sorry for the noise, but from the docs and the code that i’ve looked through, it appears that the current shareable config capability assumes that the config file to be extended is a local file.

i’d like to put together an npm package that i use across my projects, but i’m just wanting to confirm support before i put in the effort. ideally, i’d love for support to follow the conventions that have emerged in projects like eslint, commitlint, semantic-release, and others where a package named <tool-name>-config-<config-name> could be extended by using "extends": "<config-name>". for a concrete example, i’d like to publish markdownlint-config-travi and use it in my .markdownlintrc as "extends": "travi"

is this possible today? if not, would it be an enhancement that you’d consider?

[DavidAnson]

Okay, thanks. Glad you found something that suits your needs!

[travi]

my needs ended up becoming more complex, so i ended up switching to remark. i’ll close since i wont need this anymore, but certainly feel free to reopen if you still think this will be useful for the project.