<isd>
Anything that got removed it would have been because the file wasn't present on my system when I built it.
<ocdtrekkie>
And I mean, you built the last one, so I wouldn't expect a ton of extras to begin with. But some of those definitely seem silly for the package to include (tweetnacl?)
<isd>
I wonder if the last time I built this I had some extra packages pulled in from experimentation or older versions or something.
<isd>
I don't the the aws stuff is anything we might care about, for example.
<ocdtrekkie>
Right
<ocdtrekkie>
Some of the os.tmpdir or request or whatever gave me more pause.
<isd>
I did move over to a new laptop since I last built it, so some of those could have just been junk files that didn't show up again when I built from scratch.
<ocdtrekkie>
It's a vagrant-spk build though, so in theory it should only be installing the same crud more or less, because it's pulling from it's own VM.
<ocdtrekkie>
I think I am okay just approving it as "fun weirdness" and seeing if anything does end up cropping up.
<isd>
Note that node_modules is `alwaysInclude`-ed, so I think this shouldn't have a functional impact in practice anyway
<isd>
It's possible there are updated versions of some of those packages or something, which didn't get seen when I did spk dev -- but the alwaysInclude should get them.
<isd>
But yeah, I'm comfortable pulling the trigger.
<ocdtrekkie>
Alright, will try to get approvals cleaned up tonight. Maybe will see if I can do a vagrant-spk release too, but I expect to slam into bitrot there.