Broken build if a dependency's package.json uses the production export conditionnitrojs/nitro · updated 4 months ago · 99% similar bugneeds investigation
Conditional imports/exports for non-Node targets within export map are incorrectly resolvednitrojs/nitro · updated 13 months ago · 46% similar pending triage
Package exports conflict in `nitropack build`?nitrojs/nitro · updated 21 months ago · 43% similar bugcustom preset
Inject `NODE_ENV` with `production` value by default for production runtimenitrojs/nitro · updated 15 months ago · 37% similar enhancementnode
Etcd3 package is broken in server outputnitrojs/nitro · updated 21 months ago · 37% similar bugneeds investigation
Dynamic Imports Aren't Compiled (JSX)nitrojs/nitro · updated 6 months ago · 36% similar pending triage
DEP0155 and DEP0156 warnings during nitro buildnitrojs/nitro · updated 6 months ago · 35% similar nuxtpending triage
Support bundling `.node` modulesnitrojs/nitro · updated 6 months ago · 35% similar enhancementworkaround availablep2-nice-to-have
`lexical` node-specific package is not traced correctlynitrojs/nitro · updated 9 months ago · 34% similar bugworkaround availablenitro reproduction
Production builds on Windows with graphql dependency result in runtime error: Cannot find package graphqlnitrojs/nitro · updated 15 months ago · 33% similar pending triagewindowsgood reproduction :star2: