Asset Pipeline dependency installation fails on Ubuntu 23.04

[tfinnegan937]

Following the quickstart guide, I complete all of the steps up until the call to "npm install" to install the asset pipeline dependencies. It fails at that point.

Below is my full terminal output as I attempt to follow all of the steps of the guide. You will notice that after the call to npm install, I run ls on the folder that it attempts to rename, and that folder does not exist.

I am not a web developer, and I am not familiar with node.js beyond the very basics, and so I'm not sure how to get you more useful information.

tim@tim-System-Product-Name:~$ git init mygame
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint: 
hint: 	git config --global init.defaultBranch <name>
hint: 
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint: 
hint: 	git branch -m <name>
Initialized empty Git repository in /home/tim/mygame/.git/
tim@tim-System-Product-Name:~$ cd mygame
tim@tim-System-Product-Name:~/mygame$ sudo npm install @matthewcpp/framework64-cli

added 126 packages in 11s

7 packages are looking for funding
  run `npm fund` for details
tim@tim-System-Product-Name:~/mygame$ npx framework64-cli create
Creating framework64 game: mygame
framework64 project directory: /home/tim/mygame
Check for git repository in /home/tim/mygame: OK
Add framework64 submodule
Add framework64 submodule: OK
Initialize framework64 submodule
Initialize framework64 submodule: OK
Create initial commit
Create initial commit: OK
Downloading and configuring starter project from: https://github.com/matthewcpp/framework64-starter/archive/refs/heads/main.zip
Downloading and configuring starter project from: https://github.com/matthewcpp/framework64-starter/archive/refs/heads/main.zip: OK
tim@tim-System-Product-Name:~/mygame$ npm run configure-environment-n64-modernsdk

> mygame@0.0.1 configure-environment-n64-modernsdk
> node lib/framework64/scripts/ConfigureEnvironment.js n64-modernsdk

Configuring for: N64 Modern SDK
Copy: /home/tim/mygame/lib/framework64/config/n64.modernsdk/n64.modernsdk.devcontainer.json --> /home/tim/mygame/.devcontainer.json
tim@tim-System-Product-Name:~/mygame$ npm install
npm ERR! code EACCES
npm ERR! syscall rename
npm ERR! path /home/tim/mygame/node_modules/@matthewcpp/framework64-cli
npm ERR! dest /home/tim/mygame/node_modules/@matthewcpp/.framework64-cli-tUHhLoq2
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, rename '/home/tim/mygame/node_modules/@matthewcpp/framework64-cli' -> '/home/tim/mygame/node_modules/@matthewcpp/.framework64-cli-tUHhLoq2'
npm ERR!  [Error: EACCES: permission denied, rename '/home/tim/mygame/node_modules/@matthewcpp/framework64-cli' -> '/home/tim/mygame/node_modules/@matthewcpp/.framework64-cli-tUHhLoq2'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'rename',
npm ERR!   path: '/home/tim/mygame/node_modules/@matthewcpp/framework64-cli',
npm ERR!   dest: '/home/tim/mygame/node_modules/@matthewcpp/.framework64-cli-tUHhLoq2'
npm ERR! }
npm ERR! 
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR! 
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/tim/.npm/_logs/2023-07-01T05_33_35_454Z-debug-0.log
tim@tim-System-Product-Name:~/mygame$ ls /home/tim/mygame/node_modules/@mathewcpp
ls: cannot access '/home/tim/mygame/node_modules/@mathewcpp': No such file or directory

[tfinnegan937]

The quickstart guide appears to work perfectly on Windows with docker and nodejs installed, so this appears to be a linux-specific issue.

[matthewcpp]

Hi there! Thanks for reporting this. I will have to spin up a linux box and investigate...Glad it worked for you on windows!