axe-core 3.1.0 does not have main entry point `axe.js`

[ttdmayshark]

Some of our builds which leverage axe/axe-core started failing this morning with an error loading axe-core. This appears to be fallout of having moved from 3.0.3 to 3.1.0 once it was published.

• Link to live demo:
  3.0.1: https://unpkg.com/[email protected]/axe.js
  3.1.0: https://unpkg.com/[email protected]/axe.js
  3.1.0 still uses axe.js as entry point in package.json: https://unpkg.com/[email protected]/package.json

• Node version: 8.9.4

• Platform: OSX & Linux

[bjankord]

We are experiencing similar issues resolving axe-core with the latest release. It does look like this is related to the main key in the package.json pointing to axe.js, but that file doesn't look like it exists anymore in the npm package. A quick look through the code makes me think main should be updated to point to lib/core/index.js

[calinoracation]

Ours is failing as well now, but on the missing axe-core/axe.min.js file.

[ljharb]

(Please note that removing any entry point is a breaking change)

[WilcoFiers]

Hey all. Apologies for the problematic release. We are working on a fix and will have it up available within a few hours.

[WilcoFiers]

Hey all. Quick update. Axe-core 3.1.1 just landed on NPM. We should be all set to move forward again.