Improved Documentation

What's Changed

• Add better documentation by @mxdvl in #12

Full Changelog: 0.6.0...0.6.1

0.6.0

What's Changed

• Add publint link by @mxdvl in #10
• Consistent private field by @mxdvl in #11

Full Changelog: 0.5.3...0.6.0

Isomorphic Deno + Node

What's Changed

• Onboarding Ara: suggestions & node by @mxdvl in #9

Full Changelog: 0.5.1...0.5.3

Functional refactor

What's Changed

• Return list of issues by @mxdvl in #7
• New SemVer API by @mxdvl in #8

Full Changelog: 0.4.6...0.5.0

Simpler known issues specification

Any local package can have a list of packages to accept instead, for example:

{
  devDependencies: {
    "@types/package": "1.0.9",
   "package": "1.1.1"
  }
  known_issues: {
    // the contract is that both major and minor must match
    "package@1.1.1": ["@types/package@1.1.x"],
  }
}

Full Changelog: 0.3.0...v0.3.1

Package can be remote files

What's Changed

• Refactor to keep things more functional by @mxdvl in #6
• Keep things more function to allow direct consumption outside of CLI tools.

Full Changelog: 0.2.2...0.3.0

Run from deno.land

Try it today:

deno run \
	--allow-net=unpkg.com --allow-read=. \
	https://deno.land/x/package_health@0.0.2/src/main.ts \
	./package.json  \
	--cache

Testing initial release

This is minimally viable script that can be deployed in various environments.

As a simple example, which will fail with a non-zero error code if there are any health issues with your package.json

deno run \
	--allow-net=unpkg.com \
	--allow-read=. \
	https://raw.githubusercontent.com/guardian/actions-npm-dependencies/0.0.1/src/main.ts \
	package.json  \
  	--cache

Maybe we can run this from deno.land/x/ ?

What's Changed

• Health report of package.json for CI use by @mxdvl in #1

New Contributors

• @mxdvl made their first contribution in #1

Full Changelog: https://github.com/guardian/actions-npm-dependencies/commits/0.0.1