[BUGFIX] webpack detection should also consider supported versions

[stefanpenner]

No description provided.

[stefanpenner]

one of the runs failed due to what appears to be an npm issue (unrelated to this PR).... re-running

[stefanpenner]

the new failures also look spurious. One looks suspicious but doesn't appear to be reproducible locally https://github.com/ef4/ember-auto-import/pull/414/checks?check_run_id=2833013788

Should I just re-roll the CI dice? Is this instability common?

[ef4]

I think those fastboot failures are real and probably caused by upstream changes in a fastboot-related package. You may not see them locally if you're installing via lockfile.

[stefanpenner]

I think those fastboot failures are real and probably caused by upstream changes in a fastboot-related package. You may not see them locally if you're installing via lockfile.

I'll try that

[stefanpenner]

@ef4 yup, lockfile prevented local reproduction. Thanks for pointing in that direction.

not ok 2 fastboot3-dev > it is using schema version 5
  ---
  message: "failed"
  severity: failed
  actual: 3
  expected: 5
  stack:     at Assert.equal (/Users/stefanpenner/src/ef4/ember-auto-import/node_modules/qunit/qunit/qunit.js:3072:14)

[stefanpenner]

broccoli-funnel was not pinned, rather it was a random transitive dependency that was being pulled in. The latest version changed it's API, and decoupled its "functional" api from its "classical" api. (thanks @rwjblue)

To correct this, I explicitly added broccoli-funnel as a devDep + imported it correctly

[stefanpenner]

bah, failure due to NPM install... rerunning

[stefanpenner]

green! @ef4 I don't have release bit on NPM, so I'll leave that to you :)