KRAFT-LIB-CREATE(1)

πŸ“¦ version 0.12.16, in nixos 26.05, nixpkgs unstable

πŸ’… KRAFT-LIB-CREATE πŸ’…

okay bestie, welcome to the KraftKit CLI manual (that's the KraftKit Manual page you're on rn) β€” this one is all about kraft-lib-create, and honestly? it's a whole moment. πŸŽ€


✨ NAME ✨

kraft-lib-create β€” literally initializes a library from a template. that's it. that's the vibe. πŸ¦‹


🌸 SYNOPSIS 🌸

kraft lib create [FLAGS] [NAME]

flags first, name optional, main character energy always. πŸ’…


🫢 DESCRIPTION 🫢

it creates a library template. no cap, that is genuinely the entire description β€” the manpage said it in five words and honestly? respect. so bestie, you run it, you get a library template. slay. ✨


πŸ‘‘ OPTIONS πŸ‘‘

okay this is the part where you screenshot and send to the group chat, because there are a lot of them and they all matter:

  • --author-email="" β€” sets the author email to the template. put your real one in, i'm begging πŸ™ˆ
  • --author-name="" β€” sets the author name to the template. your name, in lights. iconic ✨
  • --copyright-holder="" β€” sets the copyright holder name to the template. yes it's a whole legal thing, yes you still have to fill it in πŸ’€
  • --description="" β€” sets the description to the template. one line, make it cute πŸŽ€
  • --git-init[=false] β€” init git through the creating library. version control from day one, as you should 🫢
  • -h, --help[=false] β€” help for create. when in doubt, smash this πŸ”₯
  • --initial-branch="" β€” sets the initial branch name to the template. main girlies rise 🌈
  • --library-kname="" β€” sets the library kname to the template. yes, kname. it's a whole thing. πŸ’œ
  • --library-name="" β€” sets the library name to the template. lowkey the most important one ngl
  • --no-provide-c-main[=false] β€” do not provide C main to the template. for the library-only girlies who don't need an entry point πŸ’…
  • --origin="" β€” source code origin URL. where it came from, iykyk 🌸
  • --patch-dir[=false] β€” provide patch directory to the template. patches? provided. βœ…
  • --project-name="" β€” sets the project name to the template. name your baby 🍼
  • --project-path="" β€” where to create library. like, which directory. the location. the spot. πŸ“
  • --update-refs[=false] β€” softly pack the component so that it is available via kraft list. softly!! packing!! 🧚
  • -v, --version="" β€” sets the library version to the template. semver bestie, don't embarrass me 😭
⚠️ heads up: every one of those string options defaults to "" and every bool defaults to false. that's the literal default, not me being dramatic (this time).

πŸ”₯ EXAMPLES πŸ”₯

okay the fun part, copy-paste freely:

# Create a library template
$ kraft lib create

bare. minimal. confident. just vibes. ✨

# Create a library template with a name
$ kraft lib create sample-project

now it's got a name, so it's basically a person. sample-project is such a good name fr fr πŸ₯Ή


πŸ¦‹ SEE ALSO πŸ¦‹

  • kraft-lib(1) β€” the parent page, go read it, it's giving lore πŸ’–

πŸ“œ HISTORY πŸ“œ

1-Jan-1980 β€” Auto generated by KraftKit. so it's vintage. an elder. a classic. and yet somehow still the moment πŸ‘‘


and that's the page bestie!! πŸŽ€ this absolute queen of a document is brought to you by KraftKit Documentation, dated Jan 1980 β€” yes, that date, don't ask, it's vintage. KraftKit CLI(1) forever, mwah πŸ’‹πŸ«Άβœ¨

πŸ“¦ where this page comes from