"Most NODE_OPTIONs are not supported in packaged apps" when running cypress component testing #19229

TheDutchCoder · 2021-12-03T13:59:22Z

Current behavior

When I run npm run cypress:open-ct (or run-ct), I get an error [43901:1203/085557.424470:ERROR:node_bindings.cc(276)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.

This might be an Electron issue and it doesn't seem to affect behaviour for us.

Desired behavior

No error to be thrown

Test code to reproduce

Run the Cypress component tester

Cypress Version

9.1.0

Other

MacOS 11.6
Node v16.0.0

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

eqje · 2021-12-09T07:37:58Z

Hi @TheDutchCoder We have same problem actually - did you solve this already?

TheDutchCoder · 2021-12-11T13:30:31Z

It's still showing up, but I'm not sure if there's a newer version, will check that later.

We also get an "app quit unexpectedly" warning whenever we close Cypress.

dfdumaresq · 2021-12-21T00:41:08Z

Same for me.

Cypress Version

Cypress 9.1.1.

Other

MacOS 11.6
Node v14.17.3

Running under VSCode.

Version: 1.63.0 (Universal)

Karine-Bauch · 2022-01-11T12:35:21Z

Same for me too

Ubuntu (virtualBox)
VS CODE

russellpekala · 2022-01-13T18:06:07Z

Same here.

Cypress 9.2.1
Mac M1 latest

It seems to have affected cypress testing only on first open after clean install for me.

dfdumaresq · 2022-01-13T18:07:47Z

From my limited experience it doesn't seem to affect Cypress testing.

zigang93 · 2022-01-21T09:47:36Z

I am using yarn pnp .. encounter this issue

riboher · 2022-01-24T12:33:25Z

Same thing as @zigang93. Using yarn PnP, all of a sudden I can't init cypress whatsoever. Trying to open the desktop app is unsuccessful, seeing the same error discussed above. When running my tests in headless mode, cypress starts, but it is like no packages have been installed at all, so everything fails.

geoyws · 2022-01-27T06:36:52Z

I have the same error messages but everything still runs.

dbubenheim · 2022-01-27T07:58:42Z

Same here. Log statements are showing up, but still the test suite runs fine.

linediconsine · 2022-01-28T15:20:32Z

I had the same warning

revert to cypress 9.2.0 seem to solve this,

npm install cypress@9.2.0

giorgio-zamparelli · 2022-03-03T09:18:11Z

For me downgrading to cypress 9.2.0 did not remove the error. Tests are still passing with both 9.2.0 and 9.5.1 with the error.

ericblade · 2022-03-09T03:14:15Z

9.5.1 reports this to me every time i run it. The first time, it crashed immediately upon printing this message, afterwards it runs fine.

david-d-an · 2022-04-20T17:29:17Z

I get the error only on M1 Mac but Intel Mac doesn't throw any errors. The same Node version (14.16.1), same code, same packages. Only difference is M1 and Intel chips. Is anyone having trouble on Intel Mac?

CallumHoward · 2022-04-20T23:12:49Z

@dong82 I'm seeing it on Intel Mac with node 12 (so old, I know).

david-d-an · 2022-04-20T23:39:36Z

M1 issue was addressed by Cypress themselves. See their article here.

apaatsio · 2022-05-04T14:27:25Z

The error doesn't seem to affect the test run. But to get rid of it anyway, for me it helped just to unset the environment variable before running cypress.

unset NODE_OPTIONS

FWIW, I'm using cypress 8.6.0 on an Intel Mac.

vinayg-cp · 2022-05-12T09:03:00Z

The error doesn't seem to affect the test run. But to get rid of it anyway, for me it helped just to unset the environment variable before running cypress.

unset NODE_OPTIONS

FWIW, I'm using cypress 8.6.0 on an Intel Mac.

This worked for me.

wmadden · 2022-06-15T17:08:34Z

FYI NODE_OPTIONS is set by Yarn to add the PnP module loader to Node when you use yarn exec, so if you're using Yarn PnP you probably shouldn't unset it. Even if you're not using PnP it's probably worth checking what value it's set to 🤷🏻

mehrshadFarzaneh · 2022-09-20T15:36:48Z

I solved this problem
But the point is that I use Angular version 14

I run the commandng e2eto solve this problem
Then I selected cypress among the suggested options in the command line

lmiller1990 · 2023-04-07T00:10:03Z

I am also running into this, I think NODE_OPTIONS is not getting respected (which yarn uses to set the --require for their PnP feature) which is why #25960 is a problem.

I am trying to find out how to fix this. The warning is from Electron: https://www.electronjs.org/docs/latest/api/environment-variables#node_options. Specifically

NODE_OPTIONS are explicitly disallowed in packaged apps, except for the following:

--max-http-header-size
--http-parser

Hmm, wonder if we can make this work somehow.

radthenone · 2023-04-24T15:53:21Z

i have this same problem used docker and vite

MikeMcC399 · 2023-05-05T08:23:11Z

This issue also affects Cypress E2E tests using Yarn Modern pnp. It is not restricted to CT.

lmiller1990 · 2023-05-08T00:14:15Z

Is this causing anyone to be unable to run tests or is mostly a style thing (eg - you don't like seeing a warning, even if it has no impact on you runs)?

MikeMcC399 · 2023-05-08T04:38:54Z

@lmiller1990

Is this causing anyone to be unable to run tests or is mostly a style thing (eg - you don't like seeing a warning, even if it has no impact on you runs)?

I haven't seen any test impact. The Electron warning always appears with Yarn Plug'n'Play, presumably because Electron is always used in the first phase, even if subsequently another browser is used for tests.

AlexPandovich · 2023-05-16T16:49:14Z

Hello

I have similar issue with running nodemon as debug configuration for VS code on Windows10 for Node.js by using .vscode/launch.json:

{
	"version": "0.2.0",
	"configurations": [
		{
			"type": "node",
			"request": "launch",
			"name": "nodemon",
			"runtimeExecutable": "${workspaceFolder}/node_modules/nodemon/bin/nodemon.js",
			"restart": true,
			"console": "integratedTerminal",
			"internalConsoleOptions": "neverOpen"
		}
	]
}

In my case:

remove nodemon from dev dependecies.(npm uninstall -D nodemon)
install it as global package (npm install -g nodemon)
change "runtimeExecutable": "${workspaceFolder}/node_modules/nodemon/bin/nodemon.js", to "runtimeExecutable": "nodemon",

Command line changed
from:
:${env:NODE_OPTIONS}='--require "c:/Users/38098/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/ms-vscode.js-debug/src/bootloader.js" --inspect-publish-uid=http'; ${env:VSCODE_INSPECTOR_OPTIONS}='{"inspectorIpc":"\\.\pipe\node-cdp.18452-04647856-1.sock","deferredMode":false,"waitForDebugger":"","execPath":"C:\Program Files\nodejs\node.exe","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"C:\Users\38098\AppData\Local\Temp\node-debug-callback-5477a4347fa4ae67"}';
& 'D:\projects\4-nodejs-demo-3/node_modules/nodemon/bin/nodemon.js'

to:
${env:NODE_OPTIONS}='--require "c:/Users/38098/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/ms-vscode.js-debug/src/bootloader.js" --inspect-publish-uid=http'; ${env:VSCODE_INSPECTOR_OPTIONS}='{"inspectorIpc":"\\.\pipe\node-cdp.7668-3e75cba0-11.sock","deferredMode":false,"waitForDebugger":"","execPath":"C:\Program Files\nodejs\node.exe","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"C:\Users\38098\AppData\Local\Temp\node-debug-callback-03f1f420e5a7512e"}';
& 'C:\Users\38098\AppData\Roaming\npm\nodemon.cmd'

And it starts to work.

safydy · 2023-07-26T16:43:28Z

For my case, I was using "cypress": "^12.17.2",

So I changed the version manually to "cypress": "^9.2.0" (according to "Most NODE_OPTIONs are not supported in packaged apps" when running cypress component testing #19229 (comment)),
then yarn install
change it back to "^12.17.2", then yarn install

Nothing has changed on my yarn.lock, but that workaround did resolve my issue. Very strange !!!

AStoker · 2023-09-21T15:41:11Z

Adding my voice to the group. Experiencing this with latest version of Cypress (^13.0.0).
Our setup is using NX to create an single Angular application. We then set up Yarn PnP, and then ran the cypress command to configure component tests (yarn nx g @nx/angular:cypress-component-configuration --project=my-project --build-target=my-projectr:build).

We then get this

[50088:0921/113920.188:ERROR:node_bindings.cc(300)] Most NODE_OPTIONs are not supported in packaged apps. See documentation for more details.

Followed by this

DevTools listening on ws://127.0.0.1:53068/devtools/browser/60158d19-8ee0-4092-bc24-6df5ffca7643
Your configFile is invalid: C:\Projects\***\cypress.config.ts

It threw an error when required, check the stack trace below:

TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for C:\Projects\***\cypress.config.ts
    at new NodeError (node:internal/errors:405:5)
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:99:9)
    at defaultGetFormat (node:internal/modules/esm/get_format:142:36)
    at defaultLoad (node:internal/modules/esm/load:91:20)
    at nextLoad (node:internal/modules/esm/hooks:733:28)
    at load$1 (file:///C:/***/.pnp.loader.mjs:1456:12)
    at nextLoad (node:internal/modules/esm/hooks:733:28)
    at Hooks.load (node:internal/modules/esm/hooks:377:26)
    at MessagePort.handleMessage (node:internal/modules/esm/worker:168:24)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:778:20)

MikeMcC399 · 2023-09-21T15:45:55Z

@AStoker

It seems your issue is related to Your configFile is invalid [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" #27450

TheDirigible · 2024-02-03T00:08:38Z

Still happening with the latest version.

illegalnumbers · 2024-03-04T19:33:00Z

I also see this on latest

adico1 · 2024-03-15T19:26:53Z

I also see this on latest

+1

irv-armenta-g · 2024-06-18T13:43:12Z

+1

mjhenkes added type: bug stage: ready for work The issue is reproducible and in scope labels Jan 14, 2022

JustinBeaudry mentioned this issue Mar 23, 2022

Update editable.tsx: auto-focus fix for end of line with several chil… ianstormtaylor/slate#4695

Open

cypress-bot bot added stage: backlog and removed stage: ready for work The issue is reproducible and in scope labels Apr 29, 2022

amehta265 mentioned this issue Nov 1, 2022

ERR_UNKNOWN_FILE_EXTENSION with Typescript config and Yarn 3 / Zero install #24209

Closed

nagash77 added the prevent-stale mark an issue so it is ignored by stale[bot] label Apr 3, 2023

nagash77 removed the prevent-stale mark an issue so it is ignored by stale[bot] label Apr 24, 2023

nagash77 added CT Issue related to component testing Triaged Issue has been routed to backlog. This is not a commitment to have it prioritized by the team. labels Apr 24, 2023

MikeMcC399 mentioned this issue May 4, 2023

feat: add yarn modern pnp support cypress-io/github-action#599

Merged

MikeMcC399 mentioned this issue May 18, 2023

Add Yarn Plug'n'Play note to Module API guide cypress-io/cypress-documentation#5254

Merged

jennifer-shehane removed the stage: backlog label Nov 28, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

"Most NODE_OPTIONs are not supported in packaged apps" when running cypress component testing #19229

"Most NODE_OPTIONs are not supported in packaged apps" when running cypress component testing #19229

TheDutchCoder commented Dec 3, 2021

eqje commented Dec 9, 2021

TheDutchCoder commented Dec 11, 2021

dfdumaresq commented Dec 21, 2021 •

edited

Loading

Karine-Bauch commented Jan 11, 2022

russellpekala commented Jan 13, 2022 •

edited

Loading

dfdumaresq commented Jan 13, 2022

zigang93 commented Jan 21, 2022

riboher commented Jan 24, 2022

geoyws commented Jan 27, 2022

dbubenheim commented Jan 27, 2022

linediconsine commented Jan 28, 2022

giorgio-zamparelli commented Mar 3, 2022

ericblade commented Mar 9, 2022

david-d-an commented Apr 20, 2022

CallumHoward commented Apr 20, 2022

david-d-an commented Apr 20, 2022

apaatsio commented May 4, 2022

vinayg-cp commented May 12, 2022

wmadden commented Jun 15, 2022

mehrshadFarzaneh commented Sep 20, 2022 •

edited

Loading

lmiller1990 commented Apr 7, 2023 •

edited

Loading

radthenone commented Apr 24, 2023

MikeMcC399 commented May 5, 2023

lmiller1990 commented May 8, 2023

MikeMcC399 commented May 8, 2023 •

edited

Loading

AlexPandovich commented May 16, 2023 •

edited

Loading

safydy commented Jul 26, 2023 •

edited

Loading

AStoker commented Sep 21, 2023

MikeMcC399 commented Sep 21, 2023

TheDirigible commented Feb 3, 2024

illegalnumbers commented Mar 4, 2024

adico1 commented Mar 15, 2024

irv-armenta-g commented Jun 18, 2024

"Most NODE_OPTIONs are not supported in packaged apps" when running cypress component testing #19229

"Most NODE_OPTIONs are not supported in packaged apps" when running cypress component testing #19229

Comments

TheDutchCoder commented Dec 3, 2021

Current behavior

Desired behavior

Test code to reproduce

Cypress Version

Other

eqje commented Dec 9, 2021

TheDutchCoder commented Dec 11, 2021

dfdumaresq commented Dec 21, 2021 • edited Loading

Karine-Bauch commented Jan 11, 2022

russellpekala commented Jan 13, 2022 • edited Loading

dfdumaresq commented Jan 13, 2022

zigang93 commented Jan 21, 2022

riboher commented Jan 24, 2022

geoyws commented Jan 27, 2022

dbubenheim commented Jan 27, 2022

linediconsine commented Jan 28, 2022

giorgio-zamparelli commented Mar 3, 2022

ericblade commented Mar 9, 2022

david-d-an commented Apr 20, 2022

CallumHoward commented Apr 20, 2022

david-d-an commented Apr 20, 2022

apaatsio commented May 4, 2022

vinayg-cp commented May 12, 2022

wmadden commented Jun 15, 2022

mehrshadFarzaneh commented Sep 20, 2022 • edited Loading

lmiller1990 commented Apr 7, 2023 • edited Loading

radthenone commented Apr 24, 2023

MikeMcC399 commented May 5, 2023

lmiller1990 commented May 8, 2023

MikeMcC399 commented May 8, 2023 • edited Loading

AlexPandovich commented May 16, 2023 • edited Loading

safydy commented Jul 26, 2023 • edited Loading

AStoker commented Sep 21, 2023

MikeMcC399 commented Sep 21, 2023

TheDirigible commented Feb 3, 2024

illegalnumbers commented Mar 4, 2024

adico1 commented Mar 15, 2024

irv-armenta-g commented Jun 18, 2024

dfdumaresq commented Dec 21, 2021 •

edited

Loading

russellpekala commented Jan 13, 2022 •

edited

Loading

mehrshadFarzaneh commented Sep 20, 2022 •

edited

Loading

lmiller1990 commented Apr 7, 2023 •

edited

Loading

MikeMcC399 commented May 8, 2023 •

edited

Loading

AlexPandovich commented May 16, 2023 •

edited

Loading

safydy commented Jul 26, 2023 •

edited

Loading