`npm start validate` fails after initial clone about nps HOT 4 CLOSED

I'm not familiar with Jest, but it looks like test in question failed... the wrong way.

Received value does not match the stored snapshot 1.

    - Snapshot
    + Received

      Object {
    -   "stderr": "Unable to find JS config at "./something-that-does-not-exist.js". Attempted to require as "<projectRootDir>/cli-test/fixtures/something-that-does-not-exist.js" https://github.com/kentcdodds/p-s/blob/**v0.0.0-semantically-released**/other/ERRORS_AND_WARNINGS.md#unable-to-find-config
    +   "stderr": "Unable to find JS config at "./something-that-does-not-exist.js". Attempted to require as "<projectRootDir>/cli-test/fixtures/something-that-does-not-exist.js" https://github.com/kentcdodds/p-s/blob/**v3.0.2**/other/ERRORS_AND_WARNINGS.md#unable-to-find-config

from nps.

So really the issue is with the test.cli script which validate script calls because the bug is in the missing config test in cli.test.js. I'd suggest keeping the issue title as is in case anyone else who tries to contribute has a similar issue.

from nps.

Actually, the reason for this bug is I forgot to push a change I have locally to the version in the package.json. it should be 0.0.0-semantically-released. I'll have that fixed soon.

Thanks for reporting that!

from nps.

If you're interested, I actually went ahead and implemented a different fix such that you can keep your version number in package.json. I'll leave it up to you to reject or not. Thanks, Kent!

from nps.