[proposal] specify license directly in package.json

[dylanscott]

Hi - really appreciate this package. I was wondering if you'd be open to specifying the package licenses directly in the package.json in addition to the LICENSE file. The reason being that we use the dependency review GitHub action and its allowed-licenses check gets confused by the "SEE LICENSE IN LICENSE" value. We can add exclusions for specific packages, but specifying the license in package.json should allow it to work out-of-the-box with this check.

[dylanscott]

I also opened analogous PRs for a couple of downstream packages pulled in here, pyramation/nested-obj#1 and constructive-io/strfy-js#2

[pyramation]

really appreciate you sir! I will be taking care of ALL this today ;) stay tuned!

I'll merge your commits, and import history into a new pnpm workspace, so all the dev tools aren't so scattered, and will share the new repo here later :)

[pyramation]

Successfully published:
 - nested-obj@0.1.0
 - strfy-js@3.1.0

these two have been updated, and moved to https://github.com/hyperweb-io/dev-utils as indicated on the npm packages, let me know if you need anything else, and you can now make issues for all the utilities in that repo

I'll get on the pgsql-parser ones now...

[pyramation]

Successfully published:
 - pgsql-deparser@17.12.0
 - pgsql-parser@17.9.0
 - @pgsql/cli@1.32.0
 - pg-proto-parser@1.30.0
 - @pgsql/transform@17.9.0
 - @pgsql/traverse@17.2.0
 - @pgsql/utils@17.8.0

for pgsql-parser and pgsql-deparser — depending on which version of the parser you're using (like 14, 15,16, etc), I still need to publish those... hopefully you're on the latest

[dylanscott]

Thanks so much for the quick turnaround! We're on the latest so we're good 🙏