Thanks to visit codestin.com
Credit goes to github.com

Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Support node --conditions/-C as a NODE_OPTION. #73916

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Falven opened this issue Dec 13, 2024 · 0 comments
Closed

Support node --conditions/-C as a NODE_OPTION. #73916

Falven opened this issue Dec 13, 2024 · 0 comments
Labels
Module Resolution Module resolution (CJS / ESM, module resolving). Output Related to the the output configuration option. Runtime Related to Node.js or Edge Runtime with Next.js. SWC Related to minification/transpilation in Next.js. Turbopack Related to Turbopack with Next.js. TypeScript Related to types with Next.js. Webpack Related to Webpack with Next.js.

Comments

@Falven
Copy link

Falven commented Dec 13, 2024

Link to the code that reproduces this issue

https://github.com/Falven/turborepo/tree/feature/debugging

To Reproduce

Run Nextjs with NODE_OPTIONS -C=development

-C=development is not allowed in NODE_OPTIONS

Current vs. Expected behavior

Next.js should allow conditions, including community conditions.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Dec  6 18:56:34 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6020
  Available memory (MB): 32768
  Available CPU cores: 12
Binaries:
  Node: 22.11.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 9.13.2
Relevant Packages:
  next: 15.0.3 // There is a newer version (15.1.0) available, upgrade recommended! 
  eslint-config-next: 15.0.3
  react: 19.0.0-rc-69d4b800-20241021
  react-dom: 19.0.0-rc-69d4b800-20241021
  typescript: 5.7.2
Next.js Config:
  output: standalone

Which area(s) are affected? (Select all that apply)

Developer Experience, Module Resolution, Output (export/standalone), Runtime, Turbopack, TypeScript, SWC, Webpack

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local)

Additional context

No response
@Falven Falven added the bug Issue was opened via the bug report template. label Dec 13, 2024
@github-actions github-actions bot added Developer Experience Module Resolution Module resolution (CJS / ESM, module resolving). Output Related to the the output configuration option. Runtime Related to Node.js or Edge Runtime with Next.js. SWC Related to minification/transpilation in Next.js. Turbopack Related to Turbopack with Next.js. TypeScript Related to types with Next.js. Webpack Related to Webpack with Next.js. labels Dec 13, 2024
@samcx samcx removed Developer Experience bug Issue was opened via the bug report template. labels Jan 22, 2025
@vercel vercel locked and limited conversation to collaborators Apr 30, 2025
@timneutkens timneutkens converted this issue into discussion #78708 Apr 30, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
Module Resolution Module resolution (CJS / ESM, module resolving). Output Related to the the output configuration option. Runtime Related to Node.js or Edge Runtime with Next.js. SWC Related to minification/transpilation in Next.js. Turbopack Related to Turbopack with Next.js. TypeScript Related to types with Next.js. Webpack Related to Webpack with Next.js.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Falven @samcx