Repository navigation
fix(nix): restore the development environment - #305
Conversation
Pin nixpkgs and flake-utils so the development shell resolves the same package set across machines.
|
Hi @Tenshock, thanks for the contribution. This PR description does not match the project's PR template, so the PR has been auto-closed. Specifically:
How to fix thisPlease edit the PR description and restore the template structure. You can copy the template from Why we enforce thisPR templates exist so reviewers can understand the change without reverse-engineering the diff. Stripped-out or AI-generated boilerplate descriptions consume reviewer time without producing actionable signal. Repeated low-effort or AI-slop submissions from the same account may result in being blocked from this repository. If you believe this auto-close is in error, please leave a comment explaining and a maintainer will take a look. |
|
Thanks for updating the description — the template now looks valid. A maintainer will review from here. |
baseballyama
left a comment
There was a problem hiding this comment.
Thanks! Verified locally: pnpm install --frozen-lockfile, typecheck and build pass on pnpm 11.10.0 with no config warnings, and the moved settings resolve from pnpm-workspace.yaml.
Summary
Restores the Nix development environment on current nixpkgs, migrates the project configuration to pnpm 11, and pins flake inputs for reproducible development shells.
Motivation
direnv allowfailed becausepkgs.nodePackageswas removed from nixpkgs. The pnpm 11 configuration also produced warnings because pnpm no longer reads configuration frompackage.json#pnpm.Changes
pkgs.nodePackages.pnpmwithpkgs.pnpm_11.npmrctopnpm-workspace.yamlpackage.json#pnpmconfigurationflake.lockto pin nixpkgs and flake-utilsTesting
direnv reloadnix flake check --no-buildnix build .#devShells.x86_64-linux.default --no-linkBreaking changes
None
Checklist
I have added or updated tests for the change.I have added or updated documentation where user-visible behavior changed.If this is a user-visible change, I have runpnpm changesetand committedthe result.
If this is a breaking change, I have flagged it above and the changeset ismarked accordingly.
comments.
PR represents real work that warrants a maintainer's review, and I am
willing to defend each line in review.