BROWSER-UNPACK(1)

💖 BROWSER-UNPACK(1) 💖

okay bestie, gather round, because this lil cutie of a man page is called browser-unpack and she is so much simpler than she looks. no cap. 🫶

✨ SYNOPSIS ✨

browser-unpack [file]

that's it. that's the whole vibe check. one optional file and she's off. 👑

🌸 DESCRIPTION 🌸

so browser-unpack parses a bundle generated by browser-pack. that's the whole job, that's her main character energy, she ate and left no crumbs. 💅

what she actually does: she takes a browserified js file and outputs a json file from it. so like, bundle goes in, JSON comes out, iconic behaviour honestly.

and here's the cute part — if you don't hand her a file, she'll read from STDIN by default. she's flexible like that. no arguments? no problem, she'll just wait patiently for you to pipe something in. 🎀

🦋 EXAMPLES 🦋

okay let's watch her cook. here's a lil main.js:

$ cat main.js
var foo = require('./foo.js');
var gamma = require('gamma');
console.log(foo(gamma(2.3)));

run it with node and you get:

$ node main.js
129.50502147699586

now bundle it up with browserify:

$ browserify main.js > bundle.js

and now the round trip, the full circle moment, the slay:

$ browser-unpack < bundle.js | browser-pack | node
129.50502147699586

see that?? same number. same exact number. unpack it, repack it, run it, and it's still 129.50502147699586. that's the whole point of her existence and she is nailing it. 🔥

ngl, that pipeline is genuinely satisfying. unpack → pack → node. a little triangle of trust. 🌈

💜 SEE ALSO 💜

• browserify(1)
• browser-pack(1,)
• nodejs(1)

(and yeah bestie, browser-pack(1,) really do have that lil stray comma in there. not me fixing it, not my job, i'm just the messenger 💀)

that's the whole page, periodt. 🌸 this cutie is from 8/4/17, and she's page browser-unpack(1) in the manual, so if you ever forget, just holler man browser-unpack and she'll come running. mwah. 💖✨🦋