issue trying to deploy

[whyvrafvr]

ng deploy now generates this message using Angular 18:

❌ An error occurred when trying to deploy:
The "path" argument must be of type string. Received undefined

No problem with build:

📦 Building "my-app"
📦 Build target "my-app:build:production"
Initial chunk files | Names | Raw size | Estimated transfer size
chunk-REPPZAOL.js | - | 634.01 kB | 134.41 kB
styles-2S7CTVXQ.css | styles | 149.86 kB | 9.41 kB
main-3JVGATQH.js | main | 78.06 kB | 20.35 kB
polyfills-EONH2QZO.js | polyfills | 34.54 kB | 11.32 kB

                  | Initial total | 896.47 kB |               175.48 kB

Lazy chunk files | Names | Raw size | Estimated transfer size
chunk-5FDAASR2.js | admin-module | 223.77 kB | 67.44 kB

Application bundle generation complete. [5.396 seconds]

▲ [WARNING] bundle initial exceeded maximum budget. Budget 512.00 kB was not met by 384.47 kB with a total of 896.47 kB.

Output location: (...)

[whyvrafvr]

repo attribute is mandatory folks

[fmalcher]

As long as the project is in a git repo and angular-cli-ghpages can access git, the repo argument is optional. It looks like it cannot detect the git repo in your case.
However, without knowing the exact command or seeing a minimal reproduction, we cannot investigate the issue in any way.
I am using angular-cli-ghpages successfully in a handful of Angular 18 projects and it always worked without problems. I'm afraid this is a strange constellation on your machine.

[whyvrafvr]

could you please try with this one?
https://github.com/fairhive-labs/your-angular-project

ng deploy

❌ An error occurred when trying to deploy:
Failed to get remote.undefined.url (task must either be run in a git repository with a configured undefined remote or must be configured with the "repo" option).

% git remote -v
origin	https://github.com/fairhive-labs/your-angular-project.git (fetch)
origin	https://github.com/fairhive-labs/your-angular-project.git (push)

% git config --local --get-regexp remote
remote.origin.url https://github.com/fairhive-labs/your-angular-project.git
remote.origin.fetch +refs/heads/*:refs/remotes/origin/*
branch.master.remote origin

[fmalcher]

Thanks, I see the problem! This has something to do with the new remote option intrpduced in the latest release. This actually seems to be a bug on our side. When no remote is provided, it does not fall back to origin as described, but to undefined.

You can avoid this by providing the the remote option with origin manually in your angular.json. However, we will fix this. 🙂

[whyvrafvr]

I've quickly checked out your code and yes there are few functions in git.js handling the options settings remote to undefined

[JohannesHoppe]

Fixed in v2.0.2, via #194

[whyvrafvr]

Awesome 😎
Will check asap
Thx 🙏

[whyvrafvr]

hi @JohannesHoppe @fmalcher

I've updated this repo https://github.com/fairhive-labs/your-angular-project and unfortunately if I remove repo I still get:

Failed to get remote.undefined.url (task must either be run in a git repository with a configured undefined remote or must be configured with the "repo" option).

[JohannesHoppe]

Ok, we will investigate. But could you first explain, why you only have an entry for angular-cli-ghpages in the package-lock.json and not in the package.json?

[whyvrafvr]

maybe have a look in devDependencies...

"angular-cli-ghpages": "^2.0.2",

[JohannesHoppe]

I'm blind! 🙈

[whyvrafvr]

I mean ng add angular-cli-ghpages installs it there.

[fmalcher]

@whyvrafvr btw, as a workaround it also solves the problem if you provide the remote option. This removes the need for repo and it's a bit shorter in the config. However, we will find a solution!

[whyvrafvr]

@whyvrafvr btw, as a workaround it also solves the problem if you provide the remote option. This removes the need for repo and it's a bit shorter in the config. However, we will find a solution!

As you can see on my code, yes I figured it out like that LOL 😂

[JohannesHoppe]

Please try out v2.0.3

[whyvrafvr]

i've tested, removing repo attribute or parameter, and it works fine 👍
thx you guys.