Is vite-plugin-nitro full nitro js?

[ivanjeremic]

Is the @analogjs/vite-plugin-nitro full nitro js compatible? So, can this plugin read a nitro.config.ts, and nitro's special folders like server/utils ,plugins?

In a nitro js project everything is available to us without the need to import it like useStorage or defineEventHandler is that possible with this plugin as well? How would nitro presets work where do we define the presets and build for specific platforms? (nitro.config?

[brandonroberts]

Yes, it's fully compatible with Nitro. For API routes you can use plugins, utils, storage, etc. Additional Nitro configuration such as presets can be passed in the second argument as an object to the plugin.

nitro({ ssr: true }, { preset: 'bun' })

[ivanjeremic]

Thanks. I like the framework-agnostic examples because I use React. I hope this grows to something bigger. There is definitely potential in this plugin, allowing you to include a nitro backend to your frontend with just one plugin.

[brandonroberts]

Yep, that's the goal

[ivanjeremic]

I don't want to open any unnecessary issues on this repo before asking, you mentioned that the aim is to be fully nitro compatible. I tried to use the nitro option publicAssets and wanted at root to show a different static website like this

nitro(
			{
				ssr: true,
				entryServer: "src/main.server.tsx",
			},
			{
				output: {
					dir: ".output",
					publicDir: ".output/public",
				},
				publicAssets: [
					{ baseURL: "/", dir: resolve("./www") },
					{ baseURL: "/admin", dir: resolve("./public") },
				],
			},
		),

The www folder is my custom folder and in a normal nitro project this should work, I managed to get the website to run on /admin but now the same website is twice on root and /admin. I generally think there should be an option in vite-plugin-nitro where we can specify that specific endpoints should resolve to a static website or a server route. Is that possible somehow today?

[brandonroberts]

The public folder is already copied during the build by Vite, which explains the double copies. So you can either disable Vite's behavior or just remove the extra one from your publicAssets.