Custom target

[rtritto]

With photon we can do:

// /pages/+config.ts
export default {
  photon: {
    target: 'mytarget'
   }
 } satisfies Config

How can it be done with universal-deploy stack?

Related: vikejs/vike-photon#41 (comment)

The logic should be here: https://github.com/universal-deploy/universal-deploy/blob/66e4e004641e64cf420578910ce41e29c05c79ac/packages/vite/src/plugins/supported.ts

[brillout]

Do it in your vite.config.js, the source of truth is the Vite deployment plugin you install.

[rtritto]

I need all my exports of server entry file without using any vite deployment plugin

[rtritto]

IMO if this feautre (provided as well by photon) was removed, it should be restored.

[rtritto]

@magne4000 this feature should be easily achieved: on /pages/+config.ts → server add the support of pointer imports without :default.

[rtritto]

Another change:

vike/packages/vike/src/node/vite/plugins/pluginUniversalDeploy.ts

Line 34 in 601b60c

...universalDeploy(),

should be

-...universalDeploy(),
+...universalDeploy({ node: { importer: serverEntryId } }),

[rtritto]

Is this a typo?

https://github.com/universal-deploy/universal-deploy/blob/9016de0dc6f2c61425380282a010da80eb0ebbe3/packages/adapter-node/src/vite.ts#L41

It should be:

-const resolved = await this.resolve("@universal-deploy/node/serve", importerResolvedId ?? importer);
+const resolved = await this.resolve(importerResolvedId ?? importer);

[rtritto]

This is a solution:

// /pages/+config.ts
export {
  server: 'path-of-my-server-entry'
}

where

vike/packages/vike/src/node/vite/plugins/pluginUniversalDeploy/getServerConfig.ts

Line 10 in 601b60c

function getServerConfig(vikeConfig: VikeConfigInternal) {

set serverEntryId as 'path-of-my-server-entry'

and the handler of ud:node:entry

https://github.com/universal-deploy/universal-deploy/blob/9016de0dc6f2c61425380282a010da80eb0ebbe3/packages/adapter-node/src/vite.ts#L34

should return { id: serverEntryId }

[brillout]

@rtritto Correct me if I'm wrong but I think the bottom line here is that you want API routes. And I guess the reason you don't want to use Hono routes is because you want Filesystem Routing? In that case, you might want to consider creating a Vike extension that uses +middleware (powered by Universal Middleware) — the neat thing about this approach is that it works with any server and deployment provider.

Alternatively, if you're open to it, consider using Telefunc which IMO is superior to API routes. Honest critical feedback about Telefunc welcome.

[rtritto]

/dist/server/index.mjs is an entrypoint that can exports everything.
Exports can have multiple purpose.
The startServer can be customized on needs.

+middleware and Telefunc are a lot complex and for other use cases.
My use case is simple: /dist/server/index.mjs should respect the exports of the server entrypoint file without start the server.

[brillout]

/dist/server/index.mjs should respect the exports of the server entrypoint file without start the server.

In general, maintainers are the only ones who fully see and understand certain aspects. For that reason, it's best that they make these design decisions—especially since they often have implications that aren't immediately visible.

FYI, for maximum flexibility, one thing we're considering is supporting renderPage() in parallel to UD inside +server.js, but you'll loose zero-config integration with Vite deployment plugins (you must integrate them manually then). In the meantime, you can use renderPage() with vavite instead of using UD.

[rtritto]

In general, maintainers are the only ones who fully see and understand certain aspects. For that reason, it's best that they make these design decisions—especially since they often have implications that aren't immediately visible.

This feature blocks all my deployments on Vercel, it's crucial.

[brillout]

We provided you with many options and workarounds, I ain't sure what else we can do here.