-
Notifications
You must be signed in to change notification settings - Fork 56
Description
So what I have been doing is keeping an uncommitted
package.jsonaround the folders. For instance this inpurs-tidy:{ "name": "purs-tidy", "version": "0.7.1", "dependencies": { "purs-tidy": "0.7.1" } }When I new version comes in, I bump these numbers to match the NPM release. Following this I just run
node2nixwith the latestnode2nixversion (Node v12 is deprecated, andnode2nixseems to favor the latest maintenance version instead of latest LTS).After
node2nixdoes it's thing. I rungit checkouton thedefault.nixto keep the modifications Justin did way back when. Then I go back andnvim default.nixand edit the version number to match thepackage.jsonand generated code.I
git add *.nix,git commitand write my merge request message, thengit push github $BRANCH. The diff this creates is usually minimal which Justin tends to approve of in <48 hours because it's just a few version bumps to read on his end.
Originally posted by @toastal in #146 (comment)