-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] #300
Comments
This is the whole error log Run npm i & npm run build
sh: 1: ng: not found npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2023-07-28T02_22_41_480Z-debug-0.log |
this is the workflow file that was generated by firebase, i did not alter it from its default This file was auto-generated by the Firebase CLIhttps://github.com/firebase/firebase-toolsname: Deploy to Firebase Hosting on merge |
Heya, It could be that the GitHub action cannot find the project folder if your file structure is something like this: to fix this you can add a working directory on the run and an entry point in the with clause. Does this fix the issue on your end? Here is an example workflow: # This file was auto-generated by the Firebase CLI
# https://github.com/firebase/firebase-tools
name: Deploy to Firebase Hosting on merge
'on':
push:
branches:
- main
- development
jobs:
build_and_deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- run: npm ci && npm run build
working-directory: ./projectname(case sensitive)
- uses: FirebaseExtended/action-hosting-deploy@v0
with:
projectId: ###
entrypoint: './projectname(possibly case sensitive)'
env:
FIREBASE_CLI_EXPERIMENTS: webframeworks <- Also something I needed to add for support of angular |
I'll try it, I will say that this worked just fine with no issues a month or so ago. |
Action config
Error message
Run npm run build
sh: 1: ng: not found
Error: Process completed with exit code 127.
Expected behavior
it should deploy to my firebase hosting and update the app with the new content.
Actual behavior
the action bombs out and says it can't find angular see above.
The text was updated successfully, but these errors were encountered: