Do I need to do anything special or did I miss a step ?

the umbraco ui library is coming from somewhere odd, so for any npm install type commands you need to add --force.

Suggestion for script to detect node version and moan at you to use a newer one and exit out early perhaps ?

Did you run into this issue with long path issue when building ?

Error        System.InvalidOperationException: The item metadata "%(FullPath)" cannot be applied to the path "C:\Users\warren.buckley\.nuget\packages\umbraco.cms.staticassets\14.0.0--preview004\staticwebassets\umbraco\backoffice\packages\core\property-editor\uis\collection-view\config\bulk-action-permissions\property-editor-ui-collection-view-bulk-action-permissions.element.d.ts". Path: C:\Users\warren.buckley\.nuget\packages\umbraco.cms.staticassets\14.0.0--preview004\staticwebassets\umbraco\backoffice\packages\core\property-editor\uis\collection-view\config\bulk-action-permissions\property-editor-ui-collection-view-bulk-action-permissions.element.d.ts exceeds the OS max path limit. The fully qualified file name must be less than 260 characters.

https://cdn.discordapp.com/attachments/1202962563256553544/1202964702745862184/image.png?ex=65cf5f2f&is=65bcea2f&hm=29c992918ae2701b7f0dd88ea0d41b30ab4fb550b70a4f19049044c814ee078e&

OK easy fix - but maybe something that others may stumble across

https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry > New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" ` > -Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force

Other suggestion update the JSON schema path in `Project.Client/assets/public/umbraco-package.json`to the schema file at the root of the Website project

"$schema": "../../../Project.Website/umbraco-package-schema.json",

on the schema I don't want to reference the website project (even though that's where it ends up, because i want to build projects that ultimemtly don't need the website file 😦 - there is a bug , i think there should be a copy of that file put into the client project, so going to look at that, but thinking might put a umbraco issue in asking for that file to be written in one of the other libraries so it can end up in your client project wehn you refrence them.

Also - i have sort of moved to an entry point only approach, so you never actuall touch the umbraco-package.json file once its setup 🙂

So register or discover the types of extensions via JSON schema, move over into registration approach if you then want to

done. v0.0.8 - (its a rename of the base name really, with some bits changed in the .ts files)

And kudos 🎉for being so fast !!!

@Kevin Jump any idea what I am doing wrong ?! The JS vite build is watching with

npm run watch

from the

assets

folder inside the Client folder I am then running the site directly from Visual Studio but the changes just dont get picked up. Any thoughts on what I might have done wrong mate ?! https://cdn.discordapp.com/attachments/1202962563256553544/1204361590800121896/image.png?ex=65d47423&is=65c1ff23&hm=524681def37c6487b1f8e01f835ac8de9688d4588528234d3200b95883393947&

Hmmm I think it might be because its not watching the

public

folder

Now need to figure out when updating files in this folder that it can copy it over to wwwroot/app_plugins/packagename/

I think it's an okay compromise that vite doesn't do this out of the box

using the starter kit, vite is writing to wwwroot/app_plugins/packagename, but that project is a RCL, and the website has a dependency on that, so when the files get updated from the watch command into the RCL folder, its .net and the browser link doing the update, so its not vite watch you have to check its, visual studio's browser link