How to avoid "Invalid block! <block-name> does not exist!"?

[mmailaender]

So after setting up jsrepo init @auth/svelte in a fresh project I've called jsrepo add lib/organizations which throws the error Invalid block! convex/_generated does not exist!.

convex/_generated is an auto generated dependency on user side, that's why I have added it to the excludeBlocks section in the jsrepo-build-config.json: "excludeBlocks": ["_generated", "primitives"],. But how can I configure it, that it will be also ignored during installation in userland and don't throw an error (as it will be autogenerated from the user after he starts his dev server)?

jsrepo-build-config.json

{
	"$schema": "https://unpkg.com/jsrepo@2.4.5/schemas/registry-config.json",
	"name": "@auth/svelte",
	"version": "0.0.2",
	"readme": "README.md",
	"meta": {
		"author": "Micha Mailänder",
		"bugs": "https://github.com/mmailaender/auth/issues",
		"description": "Plug & Play Auth Widgets for your application",
		"repository": "https://github.com/mmailaender/auth",
		"tags": ["auth", "svelte", "ui", "convex", "better-auth"]
	},
	"dirs": ["./src"],
	"allowSubdirectories": true,
	"doNotListBlocks": [],
	"doNotListCategories": [],
	"listBlocks": [],
	"listCategories": [],
	"excludeDeps": ["svelte", "@sveltejs/kit"],
	"peerDependencies": {
		"svelte": "5.x.x",
		"@sveltejs/kit": "2.x.x",
		"tailwindcss": "4.x.x"
	},
	"includeBlocks": [],
	"includeCategories": [],
	"excludeBlocks": ["_generated", "primitives"],
	"excludeCategories": [],
	"preview": false,
	"includeDocs": false,
	"rules": {
		"require-local-dependency-exists": "warn",
		"no-circular-dependency": "warn",
		"no-framework-dependency": "warn"
	}
}

[ieedan]

Hmm this is weird because I don't understand how it would have let you build / publish your registry without including it if it's a dependency of another block ideally this isn't something that should ever happen in user land

[mmailaender]

I've moved "_generated", and "primitives" from excludeBlocks to doNotListBlocks. Now it's not more failing with Invalid block! convex/_generated does not exist!, instead it runs in an out of memory:

jsrepo add --verbose lib/organizations

┌   jsrepo  v2.4.5 
│
◇  Retrieved blocks from @auth/svelte
┌   jsrepo  v2.4.5 
 INFO  Attempting to add ["lib/organizations"]
 INFO  Resolving @auth/svelte
 INFO  Resolved @auth/svelte
 INFO  Fetching blocks from @auth/svelte
 INFO  Trying to fetch from https://www.jsrepo.com/api/scopes/@auth/svelte/v/latest/files/jsrepo-manifest.json
 INFO  Got a response from https://www.jsrepo.com/api/scopes/@auth/svelte/v/latest/files/jsrepo-manifest.json 200 OK
 INFO  Retrieved blocks from @auth/svelte
 INFO  Installing blocks lib/organizations

<--- Last few GCs --->

[86098:0x903f000]   134412 ms: Scavenge (interleaved) 2042.0 (2080.0) -> 2040.6 (2084.2) MB, pooled: 0 MB, 9.27 / 0.00 ms  (average mu = 0.172, current mu = 0.118) allocation failure; 
[86098:0x903f000]   140489 ms: Mark-Compact (reduce) 2041.6 (2084.2) -> 2040.7 (2078.0) MB, pooled: 0 MB, 6013.94 / 0.00 ms  (+ 3.4 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 6031 ms) (average mu = 0.064, cu

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0xe1603a node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 2: 0x11e3540 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 3: 0x11e3817 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 4: 0x14110f5  [node]
 5: 0x1411123  [node]
 6: 0x142a1fa  [node]
 7: 0x142d3c8  [node]
 8: 0x1c93091  [node]
Aborted (core dumped)

Here is also the repo if you want to test it for yourself: https://github.com/mmailaender/auth/tree/feat/jsrepo (svelte folder)
@ieedan

[mmailaender]

Only to to be extra sure:

You're not getting an OOM while running jsrepo add --verbose lib/organizations in a fresh repo?

jsrepo build in the auth repo is also working for me, except the big amount of warnings.

[ieedan]

Ah yeah I see now. It's most likely down to those circular dependencies. There is most likely a path there that ends up in an infinite loop. This could probably be fixed by adding a maximum depth guard or something but it would only stop the process not necessarily allow you to install the blocks.

[mmailaender]

Thanks for clarifying — based on what I’ve seen so far, here are some ideas that might help make the workflow smoother:

• CLI stability: jsrepo shouldn’t throw an OOM but handle circular dependencies more gracefully (e.g. with a depth guard, as you suggested, and a clear error message).
• Excluded blocks: when a block is excluded, its files should also not be required as localDependencies in jsrepo-manifest.json for other blocks. Otherwise installs break (like with convex/_generated).
• Config options:
  • "require-local-dependency-exists": "warn" — currently this lets me publish blocks even if local dependencies are missing. It should also allow installing blocks when those dependencies aren’t present.
  • "no-circular-dependency": "warn" — currently this lets me publish blocks with circular dependencies. It should also allow installing them without looping into OOM (ideally just producing a warning).
• Non-enforced local dependencies: right now localDependencies are always enforced, so the build fails if they’re missing. It might be useful to introduce something like nonEnforcedLocalDependencies (naming TBD). This would give a middle ground between disabling validation entirely with "require-local-dependency-exists": "warn" and today’s strict behavior. Dependencies like _generated could then be marked as non-enforced, so they don’t block builds or installs, while other local dependencies still benefit from strict validation.

That way, excluded or auto-generated blocks don’t block installation, and circular dependencies result in warnings instead of fatal errors.
What do you think?

[mmailaender]

Hi, just wanted to check in — have you had a chance to think about this yet?
It would be great to get it resolved since it’s currently blocking me from moving forward. I’d be happy to help contribute towards a solution, of course only if you feel the proposed direction makes sense. @ieedan

[ieedan]

I would accept a PR to fix the OOM issue.

I was also thinking about nonincluded dependencies or something need to find a nice way to do that but for now I will keep thinking about it.