You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pattern I'd like to lean into, is to have npm always 'drop in' to wireit and exploit its dependency support, meaning named npm script targets are mostly cruft I have to scroll up and down and maintain.
Experimenting with the below package.json config I received the error at bottom, requiring that there should be a matching named npm script target for every entry in wireit for a reason I don't understand. Honestly this seems totally unnecessary and will just lead to duplication, scrolling and errors for no reason that I can see (I am ready to be educated).
I would rather have this requirement removed, at least for the top-level package in a monorepo, and probably for all packages (logic would look in both scripts and in wireit). Having the targets ONLY defined in the wireit property is preferred in some or many cases.
In this context I am also desperate for features around #23 to allow wildcarding package paths, (package directories) and defining upstream packages (package dependencies that live in the same repo) so that relations can be maintained in a terse way with minimal manual duplication.
You can see how e.g. the wireit.test.dependencies has to be manually maintained, (to duplicate information already in the root package.json workspaces and monorepo folder structure) and within example:test the upstream dependencies of build ( "packages/example-consumer1:test", "packages/example-consumer2:test" ) have to be manually maintained (to duplicate information already in package.json dependencies).
Not requiring named npm scripts is another way to avoid pointless duplicate info. Would it be good to remove this code (both from wireit and from people's package.json).
[github/starter]$ npm run qa
> starter@1.0.0 qa
> wireit
❌ package.json:29:5 Script "test" not found in the scripts section of this package.json.
"test": {
~~~~~~
❌ package.json:34:5 Script "lint" not found in the scripts section of this package.json.
"lint": {
~~~~~~
The text was updated successfully, but these errors were encountered:
The pattern I'd like to lean into, is to have npm always 'drop in' to wireit and exploit its dependency support, meaning named npm script targets are mostly cruft I have to scroll up and down and maintain.
Experimenting with the below package.json config I received the error at bottom, requiring that there should be a matching named npm script target for every entry in
wireit
for a reason I don't understand. Honestly this seems totally unnecessary and will just lead to duplication, scrolling and errors for no reason that I can see (I am ready to be educated).I would rather have this requirement removed, at least for the top-level package in a monorepo, and probably for all packages (logic would look in both
scripts
and inwireit
). Having the targets ONLY defined in the wireit property is preferred in some or many cases.In this context I am also desperate for features around #23 to allow wildcarding package paths, (package directories) and defining upstream packages (package dependencies that live in the same repo) so that relations can be maintained in a terse way with minimal manual duplication.
You can see how e.g. the wireit.test.dependencies has to be manually maintained, (to duplicate information already in the root package.json workspaces and monorepo folder structure) and within example:test the upstream dependencies of
build
( "packages/example-consumer1:test", "packages/example-consumer2:test" ) have to be manually maintained (to duplicate information already in package.jsondependencies
).Not requiring named npm scripts is another way to avoid pointless duplicate info. Would it be good to remove this code (both from wireit and from people's package.json).
The text was updated successfully, but these errors were encountered: