Netlify configuration for a second framework (Svelte/Vue) INSIDE exisitng NextJS project


I have a a quite strange usecase I think and I fail to make this work so I bet some of you guys know what I should do. I have a NextJS project which is my playground/portfolio site at Now I want to dive into Svelte and/or Vue but starting off with Svelte and I’d like to implement a anchor tag in my header which says Svelte that navigates to (that is then a Svelte app, ant not NextJS).

I have a NextJS app and inside there I have created a new Svelte app.I run the following locally;
npm run dev; cd svelte;npm run dev.
Which spins up a localhost:3000 and localhost:5757. Works perfectlly and my Header I got configured like this:

			label: 'SvelteKit',
			href: process.env.SVELTE_APP_URL,
			pills: (
				<Pills variant='showcase' text='Showcase' />

With my .env.local containing localhost:5777 and my containing

Now so far so good, but wanting to deploy is where I get stuck. I have no clue how to configure my TOML or Netlify backend in such an way that it builds nextjs and svelte inside the same repo and than allows to link to the /svelte app directory inside the project. If that makes sense…

This is my repo feature branch where the Svelte app + nextjs sit. GitHub - remcostoeten/ at feature/sveltekit

I hope somebody can help me out , much appreciated. And keep in mind and sorry for my devops knowledge, even TOML files and such are completely new for me.

Edit: What even would be better to have be my nextJS app. And then have which has the Svelte app. I do have my domain bought through netlify also, for whatever that’s worth.

I’m not clear that you will be able to have one dynamic framework (Svelte/Vue) inside of a site controlled by another one (next).

Have you seen this article about how to “stitch together” two sites? While it focuses on you having two repos, you could also choose to build differently on two netlify sites from the same repo instead, and still use the proxying pattern described:

You wouldn’t even need two hostnames here - visitors would come to and the magic would happen behind the scenes to connect the subsite via our proxy redirects.

It’s not trivial - it will be some work for you to configure - but it is the most likely way I can think to get this work with the least effort.