npm start errors in okta-hosted-login

[jclasley]

Running npm start in okta-hosted-login produces this error:

❯ npm start

> @okta/samples.react.okta-hosted-login@0.3.0 start
> cross-env PORT=8080 react-app-rewired start


There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.

The react-scripts package provided by Create React App requires a dependency:

  "babel-jest": "^26.6.0"

Don't try to install it manually: your package manager does it automatically.
However, a different version of babel-jest was detected higher up in the tree:

  /Users/jonlasley/Playground/samples-js-react/okta-hosted-login/node_modules/babel-jest (version: 27.5.1)

Manually installing incompatible versions is known to cause hard-to-debug issues.

If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.

To fix the dependency tree, try following the steps below in the exact order:

  1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
  2. Delete node_modules in your project folder.
  3. Remove "babel-jest" from dependencies and/or devDependencies in the package.json file in your project folder.
  4. Run npm install or yarn, depending on the package manager you use.

In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:

  5. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
     This may help because npm has known issues with package hoisting which may get resolved in future versions.

  6. Check if /Users/jonlasley/Playground/samples-js-react/okta-hosted-login/node_modules/babel-jest is outside your project directory.
     For example, you might have accidentally installed something in your home folder.

  7. Try running npm ls babel-jest in your project folder.
     This will tell you which other package (apart from the expected react-scripts) installed babel-jest.

If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.

P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!

Running npm ls babel-jest shows a version conflict produced by the jest-watch-typeahead dependency.

❯ npm ls babel-jest
@okta/samples.react.okta-hosted-login@0.3.0 /Users/jonlasley/Playground/JS/samples-js-react/okta-hosted-login
├─┬ jest-watch-typeahead@0.6.5
│ └─┬ jest@27.5.1
│   └─┬ @jest/core@27.5.1
│     └─┬ jest-config@27.5.1
│       └── babel-jest@27.5.1
└─┬ react-scripts@4.0.3
  ├── babel-jest@26.6.3
  └─┬ jest-circus@26.6.0
    └─┬ jest-runner@26.6.3
      └─┬ jest-config@26.6.3
        └── babel-jest@26.6.3 deduped

Deleting jest-watch-typeahead from the package.json, deleting node_modules and running npm install fixed the issue.

[mraible]

To get you past this issue, you can use another sample we have at https://github.com/okta-samples/okta-react-sample. The easiest way to use/configure it is using the Okta CLI. If you install the CLI, run okta login to associate your org with it, then run okta start react.

[shuowu]

@jclasley Thanks for reporting the issue, while we are fixing it, can you use the suggestion here

If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.

as a workaround?

Internal Ref: OKTA-469447

[jclasley]

I was able to make it work by removing jest-watch-typeahead which doesn't seem to be at all critical to the repo logic. I can still run tests, just don't have the fancy typeahead in filtering tests.

[jclasley]

To get you past this issue, you can use another sample we have at https://github.com/okta-samples/okta-react-sample. The easiest way to use/configure it is using the Okta CLI. If you install the CLI, run okta login to associate your org with it, then run okta start react.

Can confirm that this worked.