I have currently latest changes from contrib
branch, but after npm i
and npm run build:for:cms
I get these errors.
Has anyone else had similar issues?
I have currently latest changes from contrib
branch, but after npm i
and npm run build:for:cms
I get these errors.
Has anyone else had similar issues?
Works for me, but I did just update npm to v11 and node to v22.
Okay, it seems this was refactored at some point, so source
folder doesn’t exists here anymore (but left over from previously v14/v15):
Probably just a note to myself remembering to do a clean clone of repository to local environment once in a while
Aah okay, that can happen yeah. I would try with a git clean
next time maybe!
Okay, it was actually mentioned down the page: Umbraco-CMS/.github/BUILD.md at contrib · umbraco/Umbraco-CMS · GitHub
It may be worth inserting a link here down to clean steps
Great you figured it out. If you upgrade a local clone to a new major, it may happen that leftover files interfere with the build. git clean -fdx
is your friend.
I set up .gitconfig
with that and other nifty aliases:
[alias]
hide = update-index --assume-unchanged
unhide = update-index --no-assume-unchanged
unhide-all = ! git ls-files -v | grep '^[a-z]' | cut -c3- | xargs git unhide --
hidden = ! git ls-files -v | grep '^h' | cut -c3-
delete-tags = ! git tag -l | xargs git tag -d
restore-remote = clean -fdx
Running git restore-remote
after that will restore everything as if it was a fresh clone.
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.