Reproduce issue for: "remote function build issues sveltekit @ 2.39.0 and up (tested up to and including 2.42.0)" #14444

[tunailgaz]

We really need a minimum reproduction (or any kind of reproduction) in that case.

Originally posted by @dummdidumm in #14444
created new project with
npx sv create

package.json

{
	"name": "build-error-reproduce",
	"private": true,
	"version": "0.0.1",
	"type": "module",
	"scripts": {
		"dev": "vite dev",
		"build": "vite build",
		"preview": "vite preview",
		"prepare": "svelte-kit sync || echo ''",
		"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
		"check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch"
	},
	"devDependencies": {
		"@sveltejs/adapter-node": "5.3.2",
		"@sveltejs/kit": "2.42.2",
		"@sveltejs/vite-plugin-svelte": "6.2.0",
		"@types/node": "22.14.1",
		"svelte": "5.39.3",
		"svelte-check": "4.3.1",
		"typescript": "5.9.2",
		"vite": "7.1.6"
	},
	"dependencies": {
		"ioredis": "^5.7.0"
	}
}

svelte.config.js

import adapter from '@sveltejs/adapter-node';
import { vitePreprocess } from '@sveltejs/vite-plugin-svelte';

/** @type {import('@sveltejs/kit').Config} */
const config = {
	// Consult https://svelte.dev/docs/kit/integrations
	// for more information about preprocessors
	preprocess: vitePreprocess(),

	kit: {
    experimental: {
      remoteFunctions: true
    },
		// adapter-auto only supports some environments, see https://svelte.dev/docs/kit/adapter-auto for a list.
		// If your environment is not supported, or you settled on a specific environment, switch out the adapter.
		// See https://svelte.dev/docs/kit/adapters for more information about adapters.
		adapter: adapter(),
    version: {
      pollInterval: 120_000
    }
	}
};

export default config;

/src/lib/remotes/auth.remote.ts

import { query } from "$app/server";
import { redisSession } from "$lib/server/redis/connection";

export const getUserSession = query(async () => {
  const session = await redisSession.get('test');
  return { session }
})

/src/lib/remote/my.custom.remote.ts

import { form } from "$app/server"
import config from "$lib/server/env";
import { getUserSession } from "$lib/remotes/auth.remote";

export const testForm = form('unchecked', async () => {
  const session = await getUserSession();
  console.log(`config: ${JSON.stringify(config)}`);
  return { success: session }
})

/src/server/redis/connection.ts

import config from '$lib/server/env';
import Redis from 'ioredis';
import { building } from '$app/environment';

const redisSession = new Redis(config.redis_session);


redisSession.on('connect', () => {
  if (building) return;
  console.info(`Redis session connected ${config.redis_session.host}:${config.redis_session.port}`);
}).on('error', (err) => {
  if (building) return;
  console.warn(`Redis session ${config.redis_session.host}:${config.redis_session.port} Error: ${err}`);
});


const redisSessionHealthCheck = () => {
  return redisSession.ping('ok');
}

export {
  redisSession,
  redisSessionHealthCheck,
};

/src/server/env.ts

const NODE_ENV = process.env.NODE_ENV!
const PROD_MODE = NODE_ENV === 'production'
export default {
  redis_session: PROD_MODE ? {
    port                : 6379, // Production
    host                : 'redis-session',
    maxRetriesPerRequest: 1
  } : {
    port                : 46322,  // Development
    host                : 'localhost',
    maxRetriesPerRequest: 1
  },
};

finally /routes/+page.svelte

<script lang="ts">
    import { testForm } from "$lib/remotes/my.custom.remote";
</script>

<section class="flex flex-wrap w-full py-4">
    <form {...testForm} class=" my-2 py-2"></form>
</section>

when you run vite build
this error happens:

> build-error-reproduce@0.0.1 build
> vite build

vite v7.1.6 building SSR bundle for production...
✓ 181 modules transformed.

node:internal/event_target:1101
  process.nextTick(() => { throw err; });
                           ^
ReferenceError [Error]: Cannot access 'config' before initialization
    at /.svelte-kit/output/server/chunks/remote-4cjdf.js:13:32
    at ModuleJob.run (node:internal/modules/esm/module_job:329:25)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:644:26)
    at async analyse (node_modules/@sveltejs/kit/src/core/postbuild/analyse.js:173:34)
    at async MessagePort.<anonymous> (node_modules/@sveltejs/kit/src/utils/fork.js:23:16)

Node.js v22.17.1

when you change my.custom.remote.ts file name to custom.remote.ts error doesnt show anymore

[johnathanludwig]

I am getting an error like this one on my app after upgrading, but do not have any remote functions named with dot notation.

I think the file renaming might be a red-herring that is somehow causing vite to bundle differently, but the reproduction will hopefully get to the root cause.

[teemingc]

Might be fixed by #14456

[johnathanludwig]

2.43.7 was just released and fixes this issue for me. Fixed by #14571.

[hanneswidrig]

@dummdidumm

I can build a repro, but I figured I'd start with describing it here.

I'm running into the same error in my application after upgrading to @sveltejs/kit 2.43.7, but not on 2.43.6. I have a remote function that references another file which is using dynamic public environment variables.

When I remove $env/dynamic/public, the build-time error goes away in 2.43.7.

// example.remote.ts

import { logger } from "$lib/logger";

export const exampleQuery = query(() => {
	logger.info("test log");
	return null;
});

// $lib/logger.ts

import { pino } from "pino";

import { env } from "$env/dynamic/public";

const logLevel = env.PUBLIC_LOG_LEVEL || "info";
export const logger = pino({ level: logLevel });

 > [build 8/8] RUN pnpm build:
0.151
0.151 > project@0.0.1 build /project
0.151 > vite build --log-level error
0.151
4.276
4.276 node:internal/event_target:1101
4.276   process.nextTick(() => { throw err; });
4.276                            ^
4.276 ReferenceError [Error]: Cannot access 'public_env' before initialization
4.276     at file:///project/.svelte-kit/output/server/chunks/chunk-3.js:3:18
4.276     at ModuleJob.run (node:internal/modules/esm/module_job:345:25)
4.276     at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:665:26)
4.276     at async analyse (file:///project/node_modules/.pnpm/@sveltejs+kit@2.43.7_@opentelemetry+api@1.9.0_@sveltejs+vite-plugin-svelte@6.2.1_svelte_1a238deda32f4c5c55d923f90b8e34c8/node_modules/@sveltejs/kit/src/core/postbuild/analyse.js:51:19)
4.276     at async MessagePort.<anonymous> (file:///project/node_modules/.pnpm/@sveltejs+kit@2.43.7_@opentelemetry+api@1.9.0_@sveltejs+vite-plugin-svelte@6.2.1_svelte_1a238deda32f4c5c55d923f90b8e34c8/node_modules/@sveltejs/kit/src/utils/fork.js:23:16)
4.276
4.276 Node.js v22.20.0
4.302  ELIFECYCLE  Command failed with exit code 1.

[teemingc]

@dummdidumm

I can build a repro, but I figured I'd start with describing it here.

I'm running into the same error in my application after upgrading to @sveltejs/kit 2.43.7, but not on 2.43.6. I have a remote function that references another file which is using dynamic public environment variables.

When I remove $env/dynamic/public, the build-time error goes away in 2.43.7.

// example.remote.ts

import { logger } from "$lib/logger";

export const exampleQuery = query(() => {
logger.info("test log");
return null;
});

// $lib/logger.ts

import { pino } from "pino";

import { env } from "$env/dynamic/public";

const logLevel = env.PUBLIC_LOG_LEVEL || "info";
export const logger = pino({ level: logLevel });

[build 8/8] RUN pnpm build:
0.151
0.151 > project@0.0.1 build /project
0.151 > vite build --log-level error
0.151
4.276
4.276 node:internal/event_target:1101
4.276 process.nextTick(() => { throw err; });
4.276 ^
4.276 ReferenceError [Error]: Cannot access 'public_env' before initialization
4.276 at file:///project/.svelte-kit/output/server/chunks/chunk-3.js:3:18
4.276 at ModuleJob.run (node:internal/modules/esm/module_job:345:25)
4.276 at async onImport.tracePromise.proto (node:internal/modules/esm/loader:665:26)
4.276 at async analyse (file:///project/node_modules/.pnpm/@sveltejs+kit@2.43.7_@opentelemetry+api@1.9.0_@sveltejs+vite-plugin-svelte@6.2.1_svelte_1a238deda32f4c5c55d923f90b8e34c8/node_modules/@sveltejs/kit/src/core/postbuild/analyse.js:51:19)
4.276 at async MessagePort. (file:///project/node_modules/.pnpm/@sveltejs+kit@2.43.7_@opentelemetry+api@1.9.0_@sveltejs+vite-plugin-svelte@6.2.1_svelte_1a238deda32f4c5c55d923f90b8e34c8/node_modules/@sveltejs/kit/src/utils/fork.js:23:16)
4.276
4.276 Node.js v22.20.0
4.302  ELIFECYCLE  Command failed with exit code 1.

I could not reproduce this by using the two code examples provided.

[am283721]

Can confirm I'm experiencing a similar issue to @hanneswidrig. Looks like someone has opened issue 14590