@lovable.dev/vite-tanstack-config 2.5.0-rc.1 → 2.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.cjs CHANGED
@@ -332,9 +332,6 @@ function defineConfig(configOrOptions = {}) {
332
332
  const { command, mode } = env;
333
333
  const isSandbox = isSandboxEnvironment();
334
334
  const isDevBuild = command === "build" && mode === "development";
335
- if (isDevBuild) {
336
- process.env.NODE_ENV = "development";
337
- }
338
335
  let options;
339
336
  if (typeof configOrOptions === "function") {
340
337
  const userConfig = await Promise.resolve(configOrOptions(env));
@@ -444,11 +441,12 @@ function defineConfig(configOrOptions = {}) {
444
441
  }
445
442
  let config = {
446
443
  define: envDefine,
447
- // NODE_ENV=development gives the client the dev react-dom DevTools needs,
448
- // but it would also make esbuild emit jsxDEV; the SSR/react-server JSX
449
- // runtime has no jsxDEV export, so jsxDev:false keeps jsx/jsxs everywhere.
450
- // keepNames keeps component names readable in the DevTools tree.
451
- ...isDevBuild ? { esbuild: { jsxDev: false, keepNames: true } } : {},
444
+ // Client-scoped so React DevTools gets the dev react-dom; a global NODE_ENV
445
+ // flip would emit jsxDEV, which the react-server SSR runtime can't resolve.
446
+ ...isDevBuild ? {
447
+ environments: { client: { define: { "process.env.NODE_ENV": JSON.stringify("development") } } },
448
+ esbuild: { keepNames: true }
449
+ } : {},
452
450
  // Match the build's CSS pipeline in dev. Vite uses PostCSS in dev and only
453
451
  // runs Lightning CSS at build, so build-time transforms (e.g. collapsing a
454
452
  // hand-written `-webkit-backdrop-filter` to the prefixed form Chrome ignores)
package/dist/index.js CHANGED
@@ -298,9 +298,6 @@ function defineConfig(configOrOptions = {}) {
298
298
  const { command, mode } = env;
299
299
  const isSandbox = isSandboxEnvironment();
300
300
  const isDevBuild = command === "build" && mode === "development";
301
- if (isDevBuild) {
302
- process.env.NODE_ENV = "development";
303
- }
304
301
  let options;
305
302
  if (typeof configOrOptions === "function") {
306
303
  const userConfig = await Promise.resolve(configOrOptions(env));
@@ -410,11 +407,12 @@ function defineConfig(configOrOptions = {}) {
410
407
  }
411
408
  let config = {
412
409
  define: envDefine,
413
- // NODE_ENV=development gives the client the dev react-dom DevTools needs,
414
- // but it would also make esbuild emit jsxDEV; the SSR/react-server JSX
415
- // runtime has no jsxDEV export, so jsxDev:false keeps jsx/jsxs everywhere.
416
- // keepNames keeps component names readable in the DevTools tree.
417
- ...isDevBuild ? { esbuild: { jsxDev: false, keepNames: true } } : {},
410
+ // Client-scoped so React DevTools gets the dev react-dom; a global NODE_ENV
411
+ // flip would emit jsxDEV, which the react-server SSR runtime can't resolve.
412
+ ...isDevBuild ? {
413
+ environments: { client: { define: { "process.env.NODE_ENV": JSON.stringify("development") } } },
414
+ esbuild: { keepNames: true }
415
+ } : {},
418
416
  // Match the build's CSS pipeline in dev. Vite uses PostCSS in dev and only
419
417
  // runs Lightning CSS at build, so build-time transforms (e.g. collapsing a
420
418
  // hand-written `-webkit-backdrop-filter` to the prefixed form Chrome ignores)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lovable.dev/vite-tanstack-config",
3
- "version": "2.5.0-rc.1",
3
+ "version": "2.5.0",
4
4
  "description": "Vite config wrapper for Lovable TanStack Start projects",
5
5
  "main": "./dist/index.cjs",
6
6
  "module": "./dist/index.js",