-
Notifications
You must be signed in to change notification settings - Fork 50
Open
Description
Description:
It would be helpful to allow the tool to run directly on the current folder without automatically triggering npm pack
.
Use Case:
I want to use this tool as part of a postbuild
script. However, the current behavior causes an infinite loop:
npm postbuild
triggersattw
attw
triggersnpm pack
npm pack
triggersnpm build
npm build
triggersnpm postbuild
- ...and the cycle repeats
Current Workaround:
To avoid this loop, I manually create a tarball and run attw
on it:
"postbuild": "tar -czf dist/archive.tgz LICENSE README.md dist/cjs dist/esm dist/umd docs package.json && npx attw --format ascii dist/archive.tgz && rm dist/archive.tgz"
Proposed Solution:
Introduce an option or flag to allow attw
to operate directly on the current directory without invoking npm pack
.
Metadata
Metadata
Assignees
Labels
No labels