COFFEE(1)

πŸ‘‘ COFFEE(1) β€” the coffee manual, but make it cute πŸ‘‘

okay so bestie, welcome to coffee(1), a User Commands girly. she is the interpreter and compiler for the CoffeeScript language. yes she runs your code, yes she compiles your code, yes she does both, she's versatile like that πŸ’…


✨ NAME ✨

coffee β€” interpreter and compiler for the CoffeeScript language 🫢


🌸 SYNOPSIS 🌸

coffee [options] path/to/script.coffee [args]

πŸ’– DESCRIPTION πŸ’–

okay so the vibe is simple: if you call coffee with no options at all, she will literally just run your script. that's it. that's the whole energy. no cap. ✨

πŸŽ€ the options, one by one, no skips πŸŽ€

  • --ast β€” generate an abstract syntax tree of nodes. the whole tree. nodes and everything. 🌳
  • -b, --bare β€” compile without a top-level function wrapper. she's going out bare-faced, no wrapper, iconic. πŸ’…
  • -c, --compile β€” compile to JavaScript and save as .js files. so your coffee becomes js, slay. πŸ”₯
  • -e, --eval β€” pass a string from the command line as input. just hand her a lil string, she'll take it from there. πŸ“
  • -h, --help β€” display this help message. hi, this is the help, you found it bestie 🫢
  • -i, --interactive β€” run an interactive CoffeeScript REPL. come hang out, type stuff, see what happens. main character energy. πŸ‘‘
  • -j, --join β€” concatenate the source CoffeeScript before compiling. all the files, one big girl. 🌈
  • -l, --literate β€” treat stdio as literate style coffeescript. lowercase "coffeescript", that's how she wrote it, i don't make the rules. πŸ“–
  • -m, --map β€” generate source map and save as .js.map files. maps! so you can find your way home. πŸ—ΊοΈ
  • -M, --inline-map β€” generate source map and include it directly in output. same map, but she's carrying it on her, inline, no separate file. πŸ’œ
  • -n, --nodes β€” print out the parse tree that the parser produces. the parser's tree. printed. that's the whole thing. 🌳
  • --nodejs β€” pass options directly to the "node" binary. straight to node, no middleman. ⭐
  • --no-header β€” suppress the "Generated by" header. bye bye header, we don't know her. πŸ™ˆ
  • -o, --output β€” set the output path or path/filename for compiled JavaScript. tell her where to put the js, she'll put the js there. πŸ“
  • -p, --print β€” print out the compiled JavaScript. just show me the js, don't write a file, i'm nosy. πŸ‘€
  • -r, --require β€” require the given module before eval or REPL. load it up first, then eval or REPL. 🧚
  • -s, --stdio β€” listen for and compile scripts over stdio. she's listening bestie, talk to her through stdio. 🎧
  • -t, --transpile β€” pipe generated JavaScript through Babel. babel gets the js after coffee's done with it. ✨
  • --tokens β€” print out the tokens that the lexer/rewriter produce. lexer and rewriter, both of them, tokens out. πŸ”€
  • -v, --version β€” display the version number. she'll tell you her version, no mystery. πŸ’–
  • -w, --watch β€” watch scripts for changes and rerun commands. she's watching. she's always watching. changes happen, commands rerun. πŸ‘οΈ

ok literally that's the whole manual, every flag, nothing skipped, i would never gatekeep a flag from you 🫢

sign-off time πŸŽ€ β€” this lil beauty is coffee version 2.7.0+dfsg1, and she's dated May 2024. that's the source, that's the version, that's the date, mwah πŸ’‹ bye bestie, go compile something iconic βœ¨πŸ’…πŸ‘‘

πŸ“¦ where this page comes from