Init failing for new sites on missing package-lock.json

This doesn't seem to be working anymore

Lines 153 to 162 in 428e645

    
           # Create a placeholder package-lock.json file if one doesn't exist. The bootstrap 
        
           # script needs one so `npm ci` will run without complaining. This only needs to be 
        
           # a skeleton file, if `packages` and `dependencies` are missing, `npmci` will 
        
           # install everything from package.json but won't rewrite package-lock.json 
        
           if [[ ! -s /usr/src/site/package-lock.json ]]; then 
        
             echo -ne "${DO}Creating placeholder ${CYAN}package-lock.json${RESET} file" 
        
             echo '{"lockfileVersion":2}' >/usr/src/site/package-lock.json 
        
             sleep 0.2s 
        
             echo -e "$DONE" 
        
           fi

Either fix that, or just run npm install in new projects as a workaround. (will that cause architecture conflicts? eg. amd64 vs. arm64?)

	# Create a placeholder package-lock.json file if one doesn't exist. The bootstrap
	# script needs one so `npm ci` will run without complaining. This only needs to be
	# a skeleton file, if `packages` and `dependencies` are missing, `npmci` will
	# install everything from package.json but won't rewrite package-lock.json
	if [[ ! -s /usr/src/site/package-lock.json ]]; then
	echo -ne "${DO}Creating placeholder ${CYAN}package-lock.json${RESET} file"
	echo '{"lockfileVersion":2}' >/usr/src/site/package-lock.json
	sleep 0.2s
	echo -e "$DONE"
	fi