create-react-app: missingDeps.some not a function

https://github.com/facebook/create-react-app/blob/69cc07f2e3400d01c5db134659c762eb850ae3c8/packages/react-dev-utils/WatchMissingNodeModulesPlugin.js#L25

I am getting

TypeError: missingDeps.some is not a function

It’s a SortableSet from here https://github.com/webpack/webpack/blob/master/lib/util/SortableSet.js and it doesn’t have a .some method, so I am not sure how to fix this.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 2
  • Comments: 20 (5 by maintainers)

Most upvoted comments

@ashnur This appears to be fixed in the Webpack 4 upgrade PR, which is available via react-dev-utils@6.0.0-next.3e165448.

Please upgrade your Node version.

The current version of react-dev-utils only supports webpack 3.

You cannot use webpack 4 unless if you re-write a significant portion of tooling yourself, or wait for the release of react-scripts@^2 (which is a couple months out).

@Timer I’m getting same issue. I’m using react-dev-utils package (5.0.1) and it’s ejected version. I tried upgrade to react-dev-utils@next as well but no luck. Can you please help?

TypeError: missingDeps.some is not a function at compiler.plugin (/hello/node_modules/react-dev-utils/WatchMissingNodeModulesPlugin.js:25:23) at _err0 (eval at create (/hello/node_modules/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:12:1) at Promise.resolve.then.then.then.then.then.then.then.then.catch.then.then.then (/hello/node_modules/html-webpack-plugin/index.js:224:11) at <anonymous> error An unexpected error occurred: "Command failed.

Finally we got this working by using 5.0.0-webpack4 of react-dev-utils-for-webpack4 package.

@vireshshah we are going to have to wait “a few months”. 😃 Until then I suggest to you to use a local copy of the repo where you can apply the patches you need. (or use an earlier version of webpack).

Unfortunately, we do not have enough information to help you. If you’re installing packages like react-dev-utils it sounds like you’re ejected, otherwise I’m not sure what you’re doing.

I’m sorry if I gave you a terse first response, but most of these issues that come through like this are related to an old Node version.

If you can replicate this with a non-ejected setup, please provide all of the information the issue template states and reproduction steps. I’ll close this until more information is provided, as this issue doesn’t seem wide-spread.

@echenley Thanks man! Next round of beers on me 🍻

Publishing that version is a few months out.