Hey all,
I’ve tried multiple times to install Forge CLI but cannot get past the point where I’m using “forge create” due to the error produced below:
Error: The "paths[1]" argument must be of type string. Received undefined
TypeError [ERR_INVALID_ARG_TYPE]: The "paths[1]" argument must be of type string. Received undefined
at resolve (node:path:1169:7)
at ComposableTemplater.downloadAndExtract (/home/parallels/.nvm/versions/node/v20.18.0/lib/node_modules/@forge/cli/node_modules/@forge/cli-shared/out/apps/template.js:117:50)
at CreateAppCommand.execute (/home/parallels/.nvm/versions/node/v20.18.0/lib/node_modules/@forge/cli/node_modules/@forge/cli-shared/out/apps/create-an-app.js:21:30)
at /home/parallels/.nvm/versions/node/v20.18.0/lib/node_modules/@forge/cli/out/command-line/register-app-commands.js:80:68
at CommandLineUI.displayProgress (/home/parallels/.nvm/versions/node/v20.18.0/lib/node_modules/@forge/cli/node_modules/@forge/cli-shared/out/ui/command-line-ui.js:59:34)
at createCommandHandler (/home/parallels/.nvm/versions/node/v20.18.0/lib/node_modules/@forge/cli/out/command-line/register-app-commands.js:80:29)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Command.actionProcessor (/home/parallels/.nvm/versions/node/v20.18.0/lib/node_modules/@forge/cli/out/command-line/command.js:252:28)
at async Command.parseAsync (/home/parallels/.nvm/versions/node/v20.18.0/lib/node_modules/@forge/cli/node_modules/commander/lib/command.js:936:5)
at async Command.parse (/home/parallels/.nvm/versions/node/v20.18.0/lib/node_modules/@forge/cli/out/command-line/command.js:154:13)
Created a second new Ubuntu VM and installed fresh, but this time did not install LTS of node, but instead version 20.18.0 as forge produced a warning stating versions other than 18 or 20 may not work
No other installations of anything have been performed, so it cannot be a contamination.
We ended up having a similar problem on windows and found it was due to not having docker installed. The package lists this as a dependency even though the guides don’t mention docker from what I read.
Hi @Jovin and @bubba. While I don’t have an answer for you quite yet, I will say that Docker is definitely not a requirement, and isn’t the cause of the problems you’re both running into. Even before, Docker wasn’t used during forge create nor forge deploy, only with forge tunnel. But to be clear, even for the tunnel, Docker is no longer required.
UPDATE:
I did run into error when using a freshly installed version of Node 20.18.0 (I’m using nvm to quickly install/switch). I then ran npm install -g @forge/cli@latest which installed Forge v10.8.0 (the latest). Received same error.
Rolled back to Forge v10.7 with npm install -g @forge/cli@10.7.0 and that seems to have addressed the issue.
I’ll submit a bug report to the team to see if they can figure out what might be behind this error.
We want to inform that we have identified issues with the latest Forge CLI version 10.8.0. We would request partners to downgrade the CLI to version 10.7.0 using npm install -g @forge/cli@10.7.0 for anyone who is on 10.8.0 version currently. You can know the current version you are in by executing the forge --version command.
Any new forge CLI install ( npm install -g @forge/cli@latest ) will automatically point to 10.7.0
We will be sharing the status page announcement in some time with all the details.
Thanks for the clarification. We had someone try 10.7.0 and we still had the issue before I rolled back to 10.6 and installed docker. Is it possible that installing behind a corporate proxy might cause this? This is the only other change besides versioning that I am aware of that might have impacted why 10.7 didn’t work for us but 10.6 did if docker is not a requirement.
Hi @DavidBrumagin, hard to say. Docker shouldn’t have any effect on this at all. However, a networking issue (due to corporate firewall/proxy rules) that blocks any communication between the Forge CLI and Atlassian could definitely have an adverse affect. I recommend trying to get back to 10.7.0 and using forge create --verbose to see if there’s anything revealed there, if you’re still encountering problems.