-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Support "*" parameter in folder paths #1994
Comments
@petergrau have you looked at using yarn workspaces or lerna to specify a glob for all your sub-projects? This way dependabot will find all the nested package.json files if you add the root one that contains the workspace config/lerna config file. For example using yarn workspaces:
{
"private": true,
"workspaces": ["libs/*"]
} |
@feelepxyz something like that would work for us but we are using |
@petergrau ah unfortunately not. Will keep an eye out for more demand as it's the first time I've come across that. |
Will be great to have. Using
When dependabot creates a PR for updating the dependencies that are present in only the child packages like |
We have a similar use case (with NX) Thanks for an awesome tool! |
In case it's helpful, I suggested some awful hacks to work around this for now here: #2178 (comment) |
Closing as a duplicate of #2178 This isn't specific to the package manager and requires some deeper changes in the way dependabot fetches the repo contents to work. We've got some ideas around how this will also play into grouped updates. We don't have any current plans on supporting |
We have several plugins in one repo that all have their own
package.json
. We would like to define one directory path that catches all of them - something like:/libs/*/
That should include then all
package.json
of the libs without having to define an entry for each of them following all the same ruleset.The text was updated successfully, but these errors were encountered: