Hanging at 'Files successfully emitted, waiting for typecheck results...' #8707

sandorvasas · 2020-03-24T11:31:26Z

3.4.1
This just started happening and can't get rid of it. Without any package changes. It had been working alright, then suddenly hangs forever. Tried npm reinstall --no-cache, updated packages to 3.4.1. Have no idea what's causing it.

Downgrading typescript (used to be 3.7.5) to 3.3 or upgrading it to 3.8.3 didn't help either. Building in node 13.7 & node 13.10, with same results.

tsconfig is the same as in the ejected CRA with additional

"experimentalDecorators": true,
    "noImplicitAny": false,
    "strictNullChecks": false

The text was updated successfully, but these errors were encountered:

sandorvasas · 2020-03-24T11:42:12Z

Resolved. I don't know what the initial problem was, since, again, I hadn't changed any packages, but I created a new CRA project with typescript and copied the libs from package.json. Works fine for now.

sandorvasas · 2020-03-24T11:49:31Z

No, sorry. It's back again. Worked for two times, and now hanging again.

ulrichb · 2020-03-24T11:53:40Z

Same here.

.. and I get ReferenceError: _createSuper is not defined right at the start-up when accessing localhost:3000.

ulrichb · 2020-03-24T11:54:33Z

Also tried to delete the babel cache.

... after reverting to 3.4.0 everything works again.

sandorvasas · 2020-03-24T12:01:53Z

Removed package-lock.json, and did an npm install --package-lock. Tried 3 times, it's working (still). Previoulsy meanwhile I had run an npm audit fix, so I believe (and hope) that breaks the compilation for CRA 3.4.1. So don't run npm audit fix people!

ulrichb · 2020-03-24T12:34:02Z

Hmmm, after deleting node_modules + package-lock.json, I get the following error now:

Module parse failed: Cannot use keyword 'await' outside an async function (85:31)
File was processed with these loaders:
 * ./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.

(Cannot use keyword 'await' outside an async function is not correct, it's indeed an async method.)

Wholteza · 2020-03-25T06:50:26Z

I'm currently experiencing the same issue with the dev server getting stuck on Files successfully emitted, waiting for typecheck results....

I tried the steps @sandorvasas noted above and it is still not fixing the issue for me.
@sandorvasas are you using any web workers with workerize perhaps?

samheutmaker · 2020-03-25T08:32:42Z

I'm seeing this same issue just pop up with the dev server. Deleted node_modules and re-installed, same result. If I let the process hang for long enough it fails with JavaScript heap out of memory.

ulrichb · 2020-03-26T17:55:49Z

I just ran another test: npm un react-scripts && npm i react-scripts@3.4.0 (re-install).

Now the start is not hanging, but I still have the ReferenceError: _createSuper is not defined error.

... so this error definitely has to do with updated indirect dependencies (probably Babel which has been updated from 7.8.x to 7.9.0).

ulrichb · 2020-03-26T17:56:45Z

=> babel/babel#11336

sandorvasas · 2020-03-27T10:15:46Z

@samheutmaker Try increasing max_old_space_size.
node --max_old_space_size=8192 scripts/start.js

C-Higgins · 2020-03-30T19:22:33Z

Can confirm this is happening as well on a fresh ejected project. It hangs on that message, but after you change a file to trigger a recompile, it stops hanging until you restart the dev server.

Wholteza · 2020-03-31T08:23:35Z

I've now tried with a fresh and empty CRA and i can confirm that for me it does not happen, exact package versions are listed below if you're interested.

However i was using workerize-loader to use a web worker to convert images to base-64 strings in the
background.

The import statement needed to use the worker was using a custom format:

import createWorker, {
  Workerized
} from "workerize-loader!./my-worker-file.worker";

And this worked because i had a custom typings file:

declare module "workerize-loader!*" {
  type AnyFunction = (...args: any[]) => any;
  type Async<F extends AnyFunction> = (
    ...args: Parameters<F>
  ) => Promise<ReturnType<F>>;

  export type Workerized<T> = Worker &
    { [K in keyof T]: T[K] extends AnyFunction ? Async<T[K]> : never };

  function createInstance<T>(): Workerized<T>;
  export = createInstance;
}

The import statement above also needed a // eslint-disable-next-line, when i removed it i saw that the error was stating that you shouldn't use custom imports to modify the webpack build.
This was build by my friend so i did not know what the effects were.

As soon as i added these files and used them in the new fresh CRA project i got locked at the message mentioned in the issue title.

It's not likely that you're facing this exact issue, but maybe you have custom typing somewhere that is causing this. I thought I'd put it here for future readers.

This will probably lead to us ejecting from CRA instead, since we have a couple of things that needs it.

Here's our exact package versions, since i did not get the error without the workerize-loader package, maybe you'd like to try the version of react-scripts we're using. Beware that we are using slightly older versions of the packages since we're hunting problems of our own with this project:

{
  "name": "my-app",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "@babel/plugin-proposal-optional-chaining": "7.7.5",
    "@mdi/js": "4.8.95",
    "@mdi/react": "1.2.1",
    "@types/jest": "24.0.17",
    "@types/node": "12.7.1",
    "@types/react": "16.9.1",
    "@types/react-dom": "16.8.5",
    "file-saver": "2.0.2",
    "moment": "2.24.0",
    "react": "16.12.0",
    "react-dom": "16.12.0",
    "react-scripts": "3.4.0",
    "typescript": "3.7.3",
    "workerize-loader": "1.1.0"
  },
  "devDependencies": {
    "@types/file-saver": "2.0.1",
    "eslint": "6.8.0"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": "react-app"
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  },
  "babel": {
    "plugins": [
      "@babel/plugin-proposal-optional-chaining"
    ]
  }
}

mrdaiking · 2020-04-02T09:51:37Z

Does anybody get this error like me? I have tried to up and downgrade the version of babel. But it still occurs? Could you help me explain exactly what is it? Thanks!

ulrichb · 2020-04-02T11:06:38Z

@KyNguyenDai => babel/babel#11336

sandorvasas · 2020-04-06T20:25:43Z

Update as of today: Appeared again. Seems totally random when it appears or goes away

pixelkritzel · 2020-05-05T20:02:45Z

Same here.

But if I run yarn tsc --noEmit it's done in a second

pixelkritzel · 2020-05-05T20:19:40Z

Even better:

I did a yarn eject and changed in webpack.config.js this line to useTypescriptIncrementalApi: false, and it works again.

Will roll back and edit inside the node_modules folder for now.

elis · 2020-05-26T19:42:48Z

I've now tried with a fresh and empty CRA and i can confirm that for me it does not happen, exact package versions are listed below if you're interested.

However i was using workerize-loader to use a web worker to convert images to base-64 strings in the
background.

The import statement needed to use the worker was using a custom format:
import createWorker, {
  Workerized
} from "workerize-loader!./my-worker-file.worker";
And this worked because i had a custom typings file:
declare module "workerize-loader!*" {
  type AnyFunction = (...args: any[]) => any;
  type Async<F extends AnyFunction> = (
    ...args: Parameters<F>
  ) => Promise<ReturnType<F>>;

  export type Workerized<T> = Worker &
    { [K in keyof T]: T[K] extends AnyFunction ? Async<T[K]> : never };

  function createInstance<T>(): Workerized<T>;
  export = createInstance;
}
The import statement above also needed a // eslint-disable-next-line, when i removed it i saw that the error was stating that you shouldn't use custom imports to modify the webpack build.
This was build by my friend so i did not know what the effects were.

As soon as i added these files and used them in the new fresh CRA project i got locked at the message mentioned in the issue title.

It's not likely that you're facing this exact issue, but maybe you have custom typing somewhere that is causing this. I thought I'd put it here for future readers.

This will probably lead to us ejecting from CRA instead, since we have a couple of things that needs it.

Here's our exact package versions, since i did not get the error without the workerize-loader package, maybe you'd like to try the version of react-scripts we're using. Beware that we are using slightly older versions of the packages since we're hunting problems of our own with this project:
{
  "name": "my-app",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "@babel/plugin-proposal-optional-chaining": "7.7.5",
    "@mdi/js": "4.8.95",
    "@mdi/react": "1.2.1",
    "@types/jest": "24.0.17",
    "@types/node": "12.7.1",
    "@types/react": "16.9.1",
    "@types/react-dom": "16.8.5",
    "file-saver": "2.0.2",
    "moment": "2.24.0",
    "react": "16.12.0",
    "react-dom": "16.12.0",
    "react-scripts": "3.4.0",
    "typescript": "3.7.3",
    "workerize-loader": "1.1.0"
  },
  "devDependencies": {
    "@types/file-saver": "2.0.1",
    "eslint": "6.8.0"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": "react-app"
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  },
  "babel": {
    "plugins": [
      "@babel/plugin-proposal-optional-chaining"
    ]
  }
}

I have a very similar issue I'm experiencing for the last couple of weeks - I was sure it's related to me importing babel/rollup in some areas of the code.

My setup is very similar with workerize loader and typescript - only that I have partial typescript throughout the app and the part loading the loader is plain jsx - so I never noticed it's related.

On top of that I'm loading the worker file twice, once as a worker and once as a regular module.

Removing the workerize loader import resolved my issue! Now simply to rewrite the API between worker and main thread.

sixhellstations · 2020-06-03T14:08:22Z

Revert to 3.4.0 solve this issue for me

facebook/create-react-app#8707 (comment)

h-morales · 2020-06-14T16:40:47Z

im trying to run a fresh install of ionic react. when running ionic serve its hanging at "Files successfully emitted, waiting for typecheck results...". everything fresh install from nodejs to ionic..

* install ncp and cross-env; update npm scripts * downgrade react scripts to 3.40 for windows; move tsnode config to file facebook/create-react-app#8707 (comment) * update circle config to run tests on windows * update windows run to use cypress orb * update windows executor * require setup for windows build * downgrade babel-loader for react-scripts 3.4.0 * setup linux and windows workflows * update windows workflow to install google chrome and run test in chrome * update windows to run against electron * wait for notifications * update with additional wait for notifications * add additional wait for notifications * add additional notifications wait * add additional assertion to make sure the list has been updated * update to fix flake * fix length counts for flake * update to fix count and waits for flake * add assertion to retry for correct count * ensure the like registers * name jobs * cypress info on Windows * disable install of google chrome on windows * wait on comment to be posted to fix flake * resolve babel/compat-data to v7.9.0 to fix failed to compile error #420 (comment) Co-authored-by: Gleb Bahmutov <gleb.bahmutov@gmail.com>

dugokontov · 2020-07-15T08:39:26Z

I had same issue. Problem in my repository was that we used to use jsDocs for type annotation in js files, and I had wrong type declaration in code, like this:

/** @type {import('./../filePath').} */
let variable;

Notice that there is nothing after .. After removing this line everything worked as expected.

Getting reports of this issue: facebook/create-react-app#8707

stale · 2020-08-23T09:06:03Z

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

stale · 2020-08-29T09:09:38Z

This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue.

rickihastings · 2020-12-07T16:59:06Z

I'm getting the same issue, tried everything in here, nothing fixes it apart from reverting which isn't ideal.

bugwheels94 · 2021-01-20T16:54:57Z

Typescript Language Server is a memory eater (2GB) and (3GB) in vscode/vim extension. Some Times this error comes up when Out of Memory Happens. Create Swap or increase memory to mitigate it. I run it in WSL so creating swap(to save RAM) worked for me.

bluenote10 · 2021-04-24T11:23:11Z

FYI I have analyzed this issue a little bit and opened #10871 to include a reproduction attempt. I'm pretty sure that it involves a race condition, so it is unlikely to reproduce the problem with 100%.

aghArdeshir · 2021-07-29T11:33:46Z

I face this too. In my case there is a lerna project with 12 packages in it. I updated one of the branches after a while (~800 file changes) and started one of the packages, it is taking forever in Files successfully emitted, waiting for typecheck results...

I expected there to be a process regarding node/typescript that is eating CPU or RAM, but there is nothing special. The simple node, npm & yarn related processes are not using CPU.

pixelkritzel · 2021-07-29T12:25:28Z

Self quote from here:

As far as I understood it, it's due to Typescripts incremental API, which is invoked by fork-ts-checker-webpack-plugin. They have an update, but it isn't part of CRA yet.

TypeStrong/fork-ts-checker-webpack-plugin#463

My personal solution is to opt out of the incremental API by patching CRA Webpack config.

https://github.com/pixelkritzel/savages/blob/master/patchWebpackConfig.js

jdkern11 · 2021-08-18T16:23:58Z

This issue began for me in one of my projects after installing typescript-plugin-css-modules. I removed this and this issue has ceased since. I do not know if this information is helpful, but I thought I would add it.

* install ncp and cross-env; update npm scripts * downgrade react scripts to 3.40 for windows; move tsnode config to file facebook/create-react-app#8707 (comment) * update circle config to run tests on windows * update windows run to use cypress orb * update windows executor * require setup for windows build * downgrade babel-loader for react-scripts 3.4.0 * setup linux and windows workflows * update windows workflow to install google chrome and run test in chrome * update windows to run against electron * wait for notifications * update with additional wait for notifications * add additional wait for notifications * add additional notifications wait * add additional assertion to make sure the list has been updated * update to fix flake * fix length counts for flake * update to fix count and waits for flake * add assertion to retry for correct count * ensure the like registers * name jobs * cypress info on Windows * disable install of google chrome on windows * wait on comment to be posted to fix flake * resolve babel/compat-data to v7.9.0 to fix failed to compile error cypress-io#420 (comment) Co-authored-by: Gleb Bahmutov <gleb.bahmutov@gmail.com>

GaneshMBabu21 · 2022-06-21T17:23:39Z

Try this guys...
npm uninstall react-scripts -S
npm i react-scripts@3.4.0
ionic serve

Getting reports of this issue: facebook/create-react-app#8707

dimahinev · 2022-12-19T18:52:05Z

Hey guys, I solved this issue with yarn.lock (or package-lock)

just use previous (working) version of lock file
clean project with this script:

rm -rf node_modules
rm -f package-lock.json
rm -f yarn.lock
npm cache clean --force

yarn install
done !

em843 · 2024-10-02T20:17:04Z

Just running npm cache clean --force fixed it for me

sandorvasas added issue: bug report needs triage labels Mar 24, 2020

ulrichb mentioned this issue Mar 27, 2020

_createSuper is not defined babel/babel#11336

Closed

kevinold pushed a commit to cypress-io/cypress-realworld-app that referenced this issue Jun 12, 2020

downgrade react scripts to 3.40 for windows; move tsnode config to file

9acf02c

facebook/create-react-app#8707 (comment)

t83714 added a commit to magda-io/magda that referenced this issue Jun 24, 2020

set CRA to 3.4.0 due to this bug: facebook/create-react-app#8707

3f98ffa

imhoffd added a commit to ionic-team/starters that referenced this issue Aug 17, 2020

fix(react): revert react-scripts to 3.4.0

7558ec9

Getting reports of this issue: facebook/create-react-app#8707

stale bot added the stale label Aug 23, 2020

stale bot closed this as completed Aug 29, 2020

NoahBres mentioned this issue Dec 30, 2020

Hanging at 'Files successfully emitted, waiting for typecheck results...' when using custom loaders #10315

Open

bluenote10 mentioned this issue Apr 24, 2021

Compilation stuck at 'Files successfully emitted, waiting for typecheck results...' caused by race condition in TypeScript + web workers context #10871

Open

bluenote10 mentioned this issue Apr 24, 2021

Attempt to fix custom loader race condition #10874

Open

wand1252 added a commit to wand1252/starters-angular-ionic-and-node that referenced this issue Aug 31, 2022

fix(react): revert react-scripts to 3.4.0

1efdee6

Getting reports of this issue: facebook/create-react-app#8707

enwong10 mentioned this issue Jun 15, 2023

[Tech Debt]: Files successfully emitted, waiting for typecheck results... CrocSwap/ambient-ts-app#2468

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Hanging at 'Files successfully emitted, waiting for typecheck results...' #8707

Hanging at 'Files successfully emitted, waiting for typecheck results...' #8707

sandorvasas commented Mar 24, 2020 •

edited

Loading

sandorvasas commented Mar 24, 2020 •

edited

Loading

sandorvasas commented Mar 24, 2020

ulrichb commented Mar 24, 2020

ulrichb commented Mar 24, 2020

sandorvasas commented Mar 24, 2020 •

edited

Loading

ulrichb commented Mar 24, 2020

Wholteza commented Mar 25, 2020

samheutmaker commented Mar 25, 2020 •

edited

Loading

ulrichb commented Mar 26, 2020

ulrichb commented Mar 26, 2020

sandorvasas commented Mar 27, 2020

C-Higgins commented Mar 30, 2020

Wholteza commented Mar 31, 2020 •

edited

Loading

mrdaiking commented Apr 2, 2020

ulrichb commented Apr 2, 2020

sandorvasas commented Apr 6, 2020

pixelkritzel commented May 5, 2020

pixelkritzel commented May 5, 2020

elis commented May 26, 2020

sixhellstations commented Jun 3, 2020

h-morales commented Jun 14, 2020

dugokontov commented Jul 15, 2020 •

edited

Loading

stale bot commented Aug 23, 2020

stale bot commented Aug 29, 2020

rickihastings commented Dec 7, 2020

bugwheels94 commented Jan 20, 2021

bluenote10 commented Apr 24, 2021

aghArdeshir commented Jul 29, 2021

pixelkritzel commented Jul 29, 2021

jdkern11 commented Aug 18, 2021

GaneshMBabu21 commented Jun 21, 2022

dimahinev commented Dec 19, 2022

em843 commented Oct 2, 2024

Hanging at 'Files successfully emitted, waiting for typecheck results...' #8707

Hanging at 'Files successfully emitted, waiting for typecheck results...' #8707

Comments

sandorvasas commented Mar 24, 2020 • edited Loading

sandorvasas commented Mar 24, 2020 • edited Loading

sandorvasas commented Mar 24, 2020

ulrichb commented Mar 24, 2020

ulrichb commented Mar 24, 2020

sandorvasas commented Mar 24, 2020 • edited Loading

ulrichb commented Mar 24, 2020

Wholteza commented Mar 25, 2020

samheutmaker commented Mar 25, 2020 • edited Loading

ulrichb commented Mar 26, 2020

ulrichb commented Mar 26, 2020

sandorvasas commented Mar 27, 2020

C-Higgins commented Mar 30, 2020

Wholteza commented Mar 31, 2020 • edited Loading

mrdaiking commented Apr 2, 2020

ulrichb commented Apr 2, 2020

sandorvasas commented Apr 6, 2020

pixelkritzel commented May 5, 2020

pixelkritzel commented May 5, 2020

elis commented May 26, 2020

sixhellstations commented Jun 3, 2020

h-morales commented Jun 14, 2020

dugokontov commented Jul 15, 2020 • edited Loading

stale bot commented Aug 23, 2020

stale bot commented Aug 29, 2020

rickihastings commented Dec 7, 2020

bugwheels94 commented Jan 20, 2021

bluenote10 commented Apr 24, 2021

aghArdeshir commented Jul 29, 2021

pixelkritzel commented Jul 29, 2021

jdkern11 commented Aug 18, 2021

GaneshMBabu21 commented Jun 21, 2022

dimahinev commented Dec 19, 2022

em843 commented Oct 2, 2024

sandorvasas commented Mar 24, 2020 •

edited

Loading

sandorvasas commented Mar 24, 2020 •

edited

Loading

sandorvasas commented Mar 24, 2020 •

edited

Loading

samheutmaker commented Mar 25, 2020 •

edited

Loading

Wholteza commented Mar 31, 2020 •

edited

Loading

dugokontov commented Jul 15, 2020 •

edited

Loading