I found npx [email protected] add table, that seems to install it, though it does give a bunch of warnings:

npm WARN EBADENGINE Unsupported engine {

npm WARN EBADENGINE package: '[email protected]',

npm WARN EBADENGINE required: { node: '>=20.18.1' },

npm WARN EBADENGINE current: { node: 'v20.11.0', npm: '10.5.1' }

npm WARN EBADENGINE }

npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated

npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported

I'll try and continue with this, but if there's a better way, please let me know. Thanks!

Yep! I'm working on updating lesson 1.4 of this series this weekend just for this, though in the updated lesson, I'll recommend sticking with Radix for the time being. Getting their Reka update working is too much of a change, and there may be several inner-component changes as well that would confuse those following this series. You can still access the documentation for the Radix version at radix.chadcn-vue.com. You can also target it via their CLI via:

npx shadcn-vue@radix <command>

I've tried getting their Reka updating working myself, and tried re-initializing - neither work without compromise. They dropped support for specifying a tsconfig.json location and will instead only check the project root for a tsconfig.json, tsconfig.web.json, or tsconfig.app.json file in that order. They have a preflight check on their CLI commands that will fail the command if the found tsconfig is missing an alias definition, which is also why it states the components.json file is incorrect despite it matching their spec.

So the only possible way to get their Reka UI update working would be to rename the AdonisJS tsconfig.json file in the root of the project to something else, as Shadcn-Vue's preflight command check will only ever find and use this tsconfig file due to its name and priority in their search.

You'd then need to move your Inertia tsconfig.json file out into the project root.

I haven't tried, but you may have luck getting things working if you move all the Shadcn-Vue stuff into the inertia folder.