Describe the bug
When you make an external config of auto
to be shared across multiple packages and specify a plugin that is relative path, the plugin is not found.
To Reproduce
auto
's configpackage.json
"auto": {
"plugins": [
"./plugins/some-plugin.js",
]
}
auto
config repo and extend the config:"auto": {
"extends": "@SCOPE",
}
npx auto shipit --dry-run
⚠ warning Could not find plugin from path: $PROJECT/plugins/some-plugin.js
Expected behavior
When using auto.extend
, the relative path-ed plugins from the configuration should be relative to itself and not the project that the auto config is installed into and extended in.
Additional context
I think a viable solution is to publish the plugins to npm, but that requires setting it up the auto config project to be a monorepo, and alias-ing the plugins so I can use itself to release itself.
This is a cool use of a shared config. gonna make this work!
Could you test out the canary version in #1717? @sethomas
@hipstersmoothie NIOCE, great success!
Confirmed:
auto-config
repo, I installed auto
's canary release, and did a canary release of my auto-config
auto-config
canary release, and tried a canary release of thatReally appreciate responses/iterations.
Awesome! Thanks for confirming
:rocket: Issue was released in v10.7.0
:rocket: