The server production entry is missing

[rtritto]

Description

Error: [@brillout/vite-plugin-server-entry@0.7.18][Wrong Usage] The server production entry is missing. If you use rollupOptions.output.entryFileNames then make sure you don't change the file name of the production server entry. One of the following is expected to exist: 
  /var/task/dist/server/entry.mjs
  /var/task/dist/server/entry.js
  /var/task/dist/server/entry.cjs
  /var/task/dist/server/entryLibraries.mjs
  /var/task/dist/server/entryLibraries.js
  /var/task/dist/server/entryLibraries.cjs
    at crawlOutDir (file:///var/task/dist/server/entrypoint.mjs:4963:3)
    at async importServerProductionEntry (file:///var/task/dist/server/entrypoint.mjs:4986:23)
    at async loadProdBuildEntry (file:///var/task/dist/server/entrypoint.mjs:5535:3)
    at async initGlobalContext (file:///var/task/dist/server/entrypoint.mjs:5520:9)
    at async initGlobalContext_renderPage (file:///var/task/dist/server/entrypoint.mjs:5509:2)
    at async renderPageServerEntryOnceBegin (file:///var/task/dist/server/entrypoint.mjs:7378:3)
    at async render (file:///var/task/dist/server/entrypoint.mjs:7366:29)

Reproduction

• Deploy https://github.com/templates-ecosystem/template-vike-solid-daisyui-hono/tree/minimal-server-vercel (commit c9c3c78) on Vercel
• Go to homepage
• See Logs

Additional information

1. I added a post build postBuild.js to copy the /dist/server to /dist/client. By this way in the Vercel dashboard, on the Source Output, you can see the content of /dist/server in the /server folder.

2. With a clean vite.config.ts having simple plugins usage (without the input option at standaloner.build and without the emit-server-entrypoint plugin), the /dist/entry.mjs is generated as:

   import "./chunks/chunk-DXM9g3cv.js";
   export {};

   Notes/observations:

   • the chunk ./chunks/chunk-DXM9g3cv.js was deleted as well by bundle=true of standaloner
   • the @brillout/vite-plugin-server-entry/crawlOutDir check should not throw because the /dist/server/entry.mjs exists

   Reproduction of clean vite.config.ts: https://github.com/templates-ecosystem/template-vike-solid-daisyui-hono/tree/minimal-server-vercel (commit 13ec207)

[rtritto]

@magne4000 +server PR did changes at vike/src/runtime/server/globalContext, please can you do some check?

Probably there is an issue when standaloner is used.

FYI @brillout @nitedani

[rtritto]

Workaround

/server/entrypoint.ts

+import 'virtual:vike:global-entry:server'
export { default as app } from './index'

export const MY_SETTING = 'MY_SETTING'

vite.config.ts

standaloner({
  bundle: {
    isolated: true,
    input: {
      entrypoint: '../dist/server/entrypoint.mjs',
-     entry: '../dist/server/entry.mjs',  // not needed anymore because it's imported by entrypoint
-     index: '../dist/server/index.mjs'  // not needed because the entrypoint.mjs is used
    }
  }
})

Commit: 1aba473

Related: https://github.com/brillout/vite-plugin-server-entry#manual-import

Note: I didn't find anything in Vike's documentation, IMO this should be documented.

[rtritto]

Perhaps (probably) this issue can be considered as an undocumented (docs, polish) instead of a bug

[brillout]

I just checked out c9c3c781fd55c9134ba6f821077d1bea6e54e8e8 but I cannot reproduce: pnpm run build then pnpm run prod works fine.

Deploy [...] on Vercel

Can you make Vercel run pnpm run build and make sure it doesn't touch node_modules/ (or just bundles it)?

The issue is probably somewhere in the Vercel build pipeline.

[brillout]

Actually, wait, since you manage the server entry yourself, you don't need @brillout/vite-plugin-server-entry's auto importer — disable it and try agin.

vike/test/disableAutoImporter/vite.config.js

Lines 6 to 8 in e168602

	vitePluginServerEntry: {
	disableAutoImport: true,
	},

Closing as I don't consider this a bug.