Exporting a svelte route that depends on lib

[simonhackler]

I am trying to export a svelte route that depends on something in $lib/components like this:
import PricingTable from '$lib/components/ui/stripe-table/pricing-table.svelte';
Which always leads to this error:

│ WARN routes/pricing-table depends on local dependency lib/components which doesn't exist require-local-dependency-exists

The block I am using exists inside the jsrepo-maifest.json and can be imported as well. I disabled the require-local-dependency-exists error, but when I try to import the route in another sveltekit project I get this error:
Invalid block! lib/components does not exist!

{
	"$schema": "https://unpkg.com/jsrepo@2.0.2/schemas/registry-config.json",
	"readme": "README.md",
    "dirs": ["./src/lib/components", "./src/lib", "./src"],
	"doNotListBlocks": [],
	"doNotListCategories": [],
	"listBlocks": ["stripe-table", "pricing-table"],
	"listCategories": [],
	"excludeDeps": [],
	"includeBlocks": [],
    "includeCategories": ["ui", "utils", "routes"],
	"excludeBlocks": [],
	"excludeCategories": [],
	"preview": false,
    "peerDependencies": {
		"svelte": "5.x.x",
		"tailwindcss": {
			"version": "3.x.x",
			"message": "Tailwindcss@v4 support is in progress see: https://github.com/huntabyte/shadcn-svelte/issues/1643"
		}
	},
    "excludeDeps": ["svelte", "@sveltejs/kit"],
    "rules": {
		"no-category-index-file-dependency": "warn",
		"no-unpinned-dependency": "warn",
		"require-local-dependency-exists": "warn",
		"max-local-dependencies": ["warn", 10],
		"no-circular-dependency": "error",
		"no-unused-block": "warn",
		"no-framework-dependency": "error"
	}
}

Not sure If i am missing something here.

[ieedan]

So trying this out myself this is one of the awkward things about jsrepo that should probably be fixed...

It doesn't handle having nested routes like this that depend on each-other very well.

I would recommend keeping your project structure as simple as possible to minimize this. I will open a PR on your repo to show you what I mean.

[ieedan]

I opened https://github.com/simonhackler/svelte-stripe-table/pull/1/files I will try and take a look at situations like this when I have the chance

[simonhackler]

Ok thanks for taking the time to check this out. I will change it then.
I think it would be nice to be able to import sveltekit but I thought about just exporting them from components somewhere as well.
Another akward thing that happens with sveltekit server.ts files is that the $types import throws error when running jsbuild since the $types files is inside the .sveltekit folder.

[ieedan]

I would probably just generally avoid trying to serve entire sveltekit pages, as stuff like your environment variables will always be broken when adding them.

It's better to just build reusable functions and serve those instead and they will be more useful to users.

Either that or have the composable bits separate and then have examples like your page in your documentation.

[simonhackler]

I think it could be very useful to have routes in there, so when I start a new Project I could for example add the login route which would setup supabase with login for me, then I could add the pricing route with stripe pricing there and maybe add a landing page route etc.
Then since the code is in my repo I can start customizing the code to my liking.

I would then never want to update the route blocks but maybe I would like to update the components. So maybe that would be not using jsrepo like it is meant to be used, or maybe this turns out to not be useful at all, but I think it could be nice.

[simonhackler]

So for example building the svelte equivalent for the supabase components.
https://supabase.com/ui/docs/nextjs/password-based-auth

[ieedan]

That's fair I personally would still try and put everything under one route cause it's easier to reason about when building the registry or looking at the project for the first time. Kinda like how shadcn has all of its registry stuff under one registry directory.

In any case I have an idea now or how I can fix this.