Closed jamesgpearce closed 2 months ago
Same here, without an explicit directory arg:
Run npx -w packages/opa-react attw --pack
npx -w packages/opa-react attw --pack
shell: /usr/bin/bash -e {0}
error while checking file:
Command failed: npm pack styra-opa-react-0.2.1.tgz
The problem seems to stem from this change, where ${filename}
causes the error. Omitting it makes the error go away, restoring the previous behavior. From the npm-pack docs it seems that the named argument should be the name of a package rather than a filename, but in either case I don't think this is needed at all for npm.
@andrewbranch , the letter v
is missing in the filename being looked up
$ attw --pack
...
ENOENT: no such file or directory, open 'express-zod-api-20.1.0.tgz'
$ ls
express-zod-api-v20.1.0.tgz
I'm using yarn v1.22.22
Workaround for yarn attw --pack
:
yarn pack # or npm pack
yarn attw *.tgz
rm *.tgz
Thanks all. I’ve deprecated v0.16.0 and pointed latest back to v0.15.3.
(using NPM)
v0.15.3:
0.16.0: