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
Currently there are two “subcommands”:
yarn2nix [./yarn.lock]
yarn2nix --template [./package.json]
We are gonna have more stuff like bundle, so we should do a (breaking) switch to subcommands now that we still can.
bundle
yarn2nix convert yarn-lock [path/to/yarn.lock]
yarn2nix convert package-json [path/to/package.json]
should give us a good first namespace for the existing (low-level) functionality, invoking yarn2nix on its own should be the same as yarn2nix --help.
yarn2nix
yarn2nix --help
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently there are two “subcommands”:
yarn2nix [./yarn.lock]
: converts the lockfile to nix code from stdoutyarn2nix --template [./package.json]
: converts the package.json to a compatible bit of metadataWe are gonna have more stuff like
bundle
, so we should do a (breaking) switch to subcommands now that we still can.yarn2nix convert yarn-lock [path/to/yarn.lock]
yarn2nix convert package-json [path/to/package.json]
should give us a good first namespace for the existing (low-level) functionality, invoking
yarn2nix
on its own should be the same asyarn2nix --help
.The text was updated successfully, but these errors were encountered: