Cannot override `clientModule` location about fastify-vite

[galvez]

Pushed v3.0.0-beta.22 to npm now, should be fixed.

Before we do the final v3.0.0 release, it should have gotten a TypeScript definition for the configuration and tests to make sure this type of problem doesn't happen again. Cheers.

[galvez]

hideaway clientModule from the user all together.

See https://github.com/fastify/vite-plugin-blueprint — personally I've moved away from this approach because I want to keep fastify-vite and fastify-dx fully transparent, but I might still revisit this.

In any case, vite-plugin-blueprint is what you need.

[galvez]

Thanks for the report, looking into this!

[galvez]

One thing to know though: clientModule expects an absolute path based on the root invite.config.js.

So if root in vite.config.js is join(<dirname>, 'client'), and your client module is client/foobar.js:

{
  clientModule: '/foobar.js'
}

[galvez]

And also, you'll have to change the path in your server vite build call in package.json.

[galvez]

Additional bit of info, the following properties can be set either at the configuration top-level or in renderer. If they're set in renderer, they take precedence over anything you've set at the top-level.

• clientModule
• createErrorHandler
• createHtmlFunction
• createHtmlTemplateFunction
• createRenderFunction
• createRoute
• createRouteHandler
• prepareClient

[dac09]

One thing to know though: clientModule expects an absolute path based on the root invite.config.js.

Useful to know, and thanks for the quick fix @galvez. Can confirm it is now working.

I wonder if it would be possible to use an absolute path instead? What I'm trying to evaluate is whether I can move the clientModule to inside the framework i.e. generate the routes, and hideaway clientModule from the user all together.

I suppose I can always generate the file in a "ignored" folder `.redwood/generatedClientModule.js' and point to it from the vite root.