We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@wakaru/unminify
Just tried out the CLI on a webpack'd chunk (Ref), and it seems that @wakaru/unminify wrapped the output directory I specified in an extra folder.
First I unpacked it:
⇒ cd ./unpacked/_next/static/chunks ⇒ npx @wakaru/unpacker 496.js -o ./496-unpacked
Then I unminified it:
⇒ npx @wakaru/unminify ./496-unpacked/* -o ./496-unminified # ..snip..
I expected that the unminified files would have been in ./496-unminified/*.js, but they actually ended up in ./496-unminified/496-unpacked/*.js
./496-unminified/*.js
./496-unminified/496-unpacked/*.js
The text was updated successfully, but these errors were encountered:
7a939b7
Fixed
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Just tried out the CLI on a webpack'd chunk (Ref), and it seems that
@wakaru/unminify
wrapped the output directory I specified in an extra folder.First I unpacked it:
⇒ cd ./unpacked/_next/static/chunks ⇒ npx @wakaru/unpacker 496.js -o ./496-unpacked
Then I unminified it:
I expected that the unminified files would have been in
./496-unminified/*.js
, but they actually ended up in./496-unminified/496-unpacked/*.js
The text was updated successfully, but these errors were encountered: