Error: spawnSync C:\Users\me\repo\oas-web\node_modules\ts-node\dist\bin.js UNKNOWN #1867

JonWallsten · 2021-02-10T12:24:17Z

Type of Issue

[x] Bug Report
[ ] Feature Request

Description

After upgradring from 11.1.2 -> 11.2.0 I'm no longer able to build our project. Compilation fails with the error message below:

------------------------------------------------------------------------------
Building entry point '@oas/web-lib-angular' 
------------------------------------------------------------------------------
✖ Compiling TypeScript sources through NGC 
ERROR: spawnSync C:\Users\me\repo\oas-web\node_modules\ts-node\dist\bin.js UNKNOWN
<ref *1> Error: spawnSync C:\Users\me\repo\oas-web\node_modules\ts-node\dist\bin.js UNKNOWN 
    at Object.spawnSync (internal/child_process.js:1067:20)
    at spawnSync (child_process.js:602:24)
    at Object.execFileSync (child_process.js:629:15)
    at StylesheetProcessor.process (C:\Users\me\repo\oas-web\packages\web-lib-angular\node_modules\src\lib\styles\stylesheet-processor.ts:40:20)
    at Object.readResource (C:\Users\me\repo\oas-web\packages\web-lib-angular\node_modules\src\lib\ts\cache-compiler-host.ts:136:47)
    at AdapterResourceLoader.preload (C:\Users\me\packages\compiler-cli\src\ngtsc\resource\src\loader.ts:80:33)
    at resolveStyleUrl (C:\Users\me\packages\compiler-cli\src\ngtsc\annotations\src\component.ts:163:43)
    at Array.map (<anonymous>)
    at ComponentDecoratorHandler.preanalyze (C:\Users\me\packages\compiler-cli\src\ngtsc\annotations\src\component.ts:186:75)
    at _loop_1 (C:\Users\me\packages\compiler-cli\src\ngtsc\transform\src\compilation.ts:312:39) {
  errno: -4094,
  code: 'UNKNOWN',
  syscall: 'spawnSync C:\\Users\\me\\repo\\oas-web\\node_modules\\ts-node\\dist\\bin.js',
  path: 'C:\\Users\\me\\repo\\oas-web\\node_modules\\ts-node\\dist\\bin.js',
  spawnargs: [
    'C:\\Users\\me\\repo\\oas-web\\packages\\web-lib-angular\\node_modules\\ng-packagr\\lib\\styles\\stylesheet-processor-worker.js',
    '{"filePath":"C:\\\\Users\\\\me\\\\repo\\\\oas-web\\\\packages\\\\web-lib-angular\\\\src\\\\components\\\\action-menu\\\\action-menu.component.scss","basePath":"C:\\\\Users\\\\me\\\\repo\\\\oas-web\\\\packages\\\\web-lib-angular","cssUrl":"inline","styleIncludePaths":[],"browserslistData":["and_chr 88","and_ff 83","and_qq 10.4","and_uc 12.12","android 81","baidu 7.12","chrome 88","chrome 87","chrome 86","edge 88","edge 87","firefox 85","firefox 84","firefox 78","ie 11","ios_saf 14.0-14.4","ios_saf 13.4-13.7","ios_saf 12.2-12.4","kaios 2.5","op_mini all","op_mob 59","opera 72","opera 71","safari 14","safari 13.1","samsung 13.0","samsung 12.0"]}'
  ],
  error: [Circular *1],
  status: null,
  signal: null,
  output: null,
  pid: 0,
  stdout: null,
  stderr: null
}

How To Reproduce

Not sure since I'm not sure what's wrong. I tried to debug with DevTools for Node.JS, but the build actually succeeded when I stepped through all the caught/uncaught exceptions. So there might be a race condition somewhere.
I can't publish our full repo since the code is not open source. But we have a pretty simple lib with some components and directives.
I'm using ts-node to inittiate ng-packagr:
cross-env NODE_ENV=development ts-node ng-packagr

//ng-packagr.ts
ngPackage
        .ngPackagr()
        .forProject('ng-package.json')
        .withTsConfig('tsconfig.build.json')
        .build()
        .catch(error => {
            console.error(error);
            process.exit(1);
        });

Expected Behaviour

The building process should finish without error.

Version Information

ng-packagr:            11.2.0 
@angular/compiler:     11.1.2 
rollup:                2.38.5
tsickle:
typescript:            4.1.4

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

SchnWalter · 2021-02-10T14:39:50Z

Are you using npm link or yarn link to install a local version of @angular/compiler-cli?

You should not see TypeScript files in your error, like: C:\Users\me\packages\compiler-cli\src\ngtsc\annotations\src\component.ts.

JonWallsten · 2021-02-10T15:12:41Z

Not deliberately at least. Can double check tomorrow, but I highly doubt it. We don't use any synlinks in our monorepo.

JonWallsten · 2021-02-10T15:13:53Z

Maybe some issue with ngcc/ivy. I'll reinstall everything tomorrow.

flash-me · 2021-02-11T08:16:43Z

Not deliberately at least. Can double check tomorrow, but I highly doubt it. We don't use any synlinks in our monorepo.

🤔 Sure there is no linking?

C:\Users\me\repo\oas-web\node_modules\....
Your workspace is at ^^^^^

But

C:\Users\me\packages\compiler-cli\...
Errors point to ^^^^^

🤷🏽‍♂️
Implicitly it's also a link If dependencies are referring to relative / absolve paths, e. g. when the cloned git repo is being used instead of a released package.

cheers
flash ⚡

JonWallsten · 2021-02-11T08:23:05Z

C:\Users\me\packages\compiler-cli\ doesn't exist. I don't have any symlinks. If that path is shown, there's probably a bug somewhere in the resolver.

We do however use a monorepo.
So my angular packages are located in C:\Users\me\repo\oas-web\node_modules and ng-packagr is located in C:\Users\me\repo\oas-web\packages\web-lib-angular\node_modules.

flash-me · 2021-02-11T08:32:19Z

Uhm alright, but how does it come that you have typescript files?
If ng-packagr is located in a node_modules directory, I assume its installed as a dependency and therefore may consist of .js and .d.ts files.
Given that, you wouldn't have to use ts-node at all?

cheers
flash ⚡

JonWallsten · 2021-02-11T08:55:27Z

I don't have any TypeScript files in C:\Users\me\repo\oas-web\node_modules\@angular\compiler-cli. Not sure why the output shows it tries to resolve those. These paths/files does not exist.
I use ts-node because I want typings in my ng-packagr.ts. But yes, I could use node and make it a js-file instead. That would however just cover up this issue.

flash-me · 2021-02-11T09:19:12Z

Not it wouldn't. These are runtime errors, ts-node would give you compile time reports. Anyway.

The issues are related to action-menu.component.scss, can you check if the component etc are valid? Are there circular Imports? (both scss and ts)

cheers
flash ⚡

JonWallsten · 2021-02-11T09:23:16Z

It builds perfectly fine when downgrading. But I will resinstall all the modules. This might be a non-issue.

SchnWalter · 2021-02-11T11:15:44Z

What happens if you change your extension to .js and run using node?

You mentioned downgrading, what version did you use before?

JonWallsten · 2021-02-12T09:00:12Z

After clearing node_modules for our entire monorepo and then reinstalling everything, including upgrading the rest of the angular components to 11.2.0 i get the same thing.

✖ Compiling TypeScript sources through NGC
ERROR: spawnSync C:\Users\me\repo\oas-web\node_modules\ts-node\dist\bin.js UNKNOWN
<ref *1> Error: spawnSync C:\Users\me\repo\oas-web\node_modules\ts-node\dist\bin.js UNKNOWN
    at Object.spawnSync (internal/child_process.js:1067:20)
    at spawnSync (child_process.js:602:24)
    at Object.execFileSync (child_process.js:629:15)
    at StylesheetProcessor.process (C:\Users\me\repo\oas-web\packages\web-lib-angular\node_modules\src\lib\styles\stylesheet-processor.ts:40:20)
    at Object.readResource (C:\Users\me\repo\oas-web\packages\web-lib-angular\node_modules\src\lib\ts\cache-compiler-host.ts:136:47)
    at AdapterResourceLoader.preload (C:\Users\me\packages\compiler-cli\src\ngtsc\resource\src\loader.ts:80:33)
    at resolveStyleUrl (C:\Users\me\packages\compiler-cli\src\ngtsc\annotations\src\component.ts:190:38)
    at C:\Users\me\packages\compiler-cli\src\ngtsc\annotations\src\component.ts:223:29
    at Array.map (<anonymous>)
    at ComponentDecoratorHandler.preanalyze (C:\Users\me\packages\compiler-cli\src\ngtsc\annotations\src\component.ts:222:35) {
  errno: -4094,
  code: 'UNKNOWN',
  syscall: 'spawnSync C:\\Users\\me\\repo\\oas-web\\node_modules\\ts-node\\dist\\bin.js',
  path: 'C:\\Users\\me\\repo\\oas-web\\node_modules\\ts-node\\dist\\bin.js',
  spawnargs: [
    'C:\\Users\\me\\repo\\oas-web\\packages\\web-lib-angular\\node_modules\\ng-packagr\\lib\\styles\\stylesheet-processor-worker.js',
    '{"filePath":"C:\\\\Users\\\\me\\\\repo\\\\oas-web\\\\packages\\\\web-lib-angular\\\\src\\\\components\\\\action-menu\\\\action-menu.component.scss","basePath":"C:\\\\Users\\\\me\\\\repo\\\\oas-web\\\\packages\\\\web-lib-angular","cssUrl":"inline","styleIncludePaths":[],"browserslistData":["and_chr 88","and_ff 83","and_qq 10.4","and_uc 12.12","android 81","baidu 7.12","chrome 88","chrome 87","chrome 86","edge 88","edge 87","firefox 85","firefox 84","firefox 78","ie 11","ios_saf 14.0-14.4","ios_saf 13.4-13.7","ios_saf 12.2-12.4","kaios 2.5","op_mini all","op_mob 59","opera 72","opera 71","safari 14","safari 13.1","samsung 13.0","samsung 12.0"]}'
  ],
  error: [Circular *1],
  status: null,
  signal: null,
  output: null,
  pid: 0,
  stdout: null,
  stderr:

It works perfectly fine with 11.1.2. So they definitely broke something in the release.
Running without ts-node works fine, but I'm using local build tools written in TypeScript, so it would be a hassle to pre-compile those compared to just running ts-node.

I will check if you can run ts-node without sourcemaps so we can get the real paths.

Closes #1867

Closes #1867 (cherry picked from commit 6a9a23d)

JonWallsten · 2021-02-12T12:11:04Z

@alan-agius4 Just wanted to confirm that it works! Thanks!

github-actions · 2021-03-15T00:33:10Z

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

_{This action has been performed automatically by a bot.}

SchnWalter mentioned this issue Feb 10, 2021

refactor: version command should display ts-node version #1868

Closed

2 tasks

alan-agius4 mentioned this issue Feb 12, 2021

fix: use path.join instead of require.resolve to resolve worker #1876

Merged

2 tasks

alan-agius4 closed this as completed in #1876 Feb 12, 2021

alan-agius4 added a commit that referenced this issue Feb 12, 2021

fix: use path.join instead of require.resolve to resolve worker

6a9a23d

Closes #1867

alan-agius4 added a commit that referenced this issue Feb 12, 2021

fix: use path.join instead of require.resolve to resolve worker

784d340

Closes #1867 (cherry picked from commit 6a9a23d)

github-actions bot locked and limited conversation to collaborators Mar 15, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: spawnSync C:\Users\me\repo\oas-web\node_modules\ts-node\dist\bin.js UNKNOWN #1867

Error: spawnSync C:\Users\me\repo\oas-web\node_modules\ts-node\dist\bin.js UNKNOWN #1867

JonWallsten commented Feb 10, 2021 •

edited

SchnWalter commented Feb 10, 2021

JonWallsten commented Feb 10, 2021

JonWallsten commented Feb 10, 2021

flash-me commented Feb 11, 2021

JonWallsten commented Feb 11, 2021 •

edited

flash-me commented Feb 11, 2021

JonWallsten commented Feb 11, 2021

flash-me commented Feb 11, 2021 •

edited

JonWallsten commented Feb 11, 2021

SchnWalter commented Feb 11, 2021 •

edited

JonWallsten commented Feb 12, 2021 •

edited

JonWallsten commented Feb 12, 2021

github-actions bot commented Mar 15, 2021

Error: spawnSync C:\Users\me\repo\oas-web\node_modules\ts-node\dist\bin.js UNKNOWN #1867

Error: spawnSync C:\Users\me\repo\oas-web\node_modules\ts-node\dist\bin.js UNKNOWN #1867

Comments

JonWallsten commented Feb 10, 2021 • edited

Type of Issue

Description

How To Reproduce

Expected Behaviour

Version Information

SchnWalter commented Feb 10, 2021

JonWallsten commented Feb 10, 2021

JonWallsten commented Feb 10, 2021

flash-me commented Feb 11, 2021

JonWallsten commented Feb 11, 2021 • edited

flash-me commented Feb 11, 2021

JonWallsten commented Feb 11, 2021

flash-me commented Feb 11, 2021 • edited

JonWallsten commented Feb 11, 2021

SchnWalter commented Feb 11, 2021 • edited

JonWallsten commented Feb 12, 2021 • edited

JonWallsten commented Feb 12, 2021

github-actions bot commented Mar 15, 2021

JonWallsten commented Feb 10, 2021 •

edited

JonWallsten commented Feb 11, 2021 •

edited

flash-me commented Feb 11, 2021 •

edited

SchnWalter commented Feb 11, 2021 •

edited

JonWallsten commented Feb 12, 2021 •

edited