You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
right now when I create a new project using angular then add nest to do there are multiple problems
the GitHub action fail by default with error fatal: ambiguous argument 'origin/main': unknown revision or path not in the working tree.
that's because the branch that nx created is master but the default branch in nrwl/nx-set-shas jon is main
I choose to playwright as my e2e it fails by default with error Executable doesn't exist at /home/runner/.cache/ms-playwright/chromium-1105/chrome-linux/chrome
the nest e2e doesn't work out of the box in the CI because it needs the API to be served first, I wasn't sure how to actually make it work so I just deleted it 😅
running nx run-many -t serve doesn't work, only the first one actually is served and it's random sometimes it's Angular and some other it's nest
Expected Behavior
create the default branch main or add main-branch-name for master in the .github/workflows/ci.yml file like what I did here robertIsaac/ng-nest-reprod@527b401
when choosing playwright as e2e, nx should by default add postinstall script npx playwright install --with-deps as I did in robertIsaac/ng-nest-reprod@a8b0207 or to add it as an extra step in the ci.yaml file
it should work out of the box
it should work for both angular and nest, this actually used to work in 17.x version, seems to be broken in 18.0 version
1.create a new project npx create-nx-workspace ng-nest-reprod then follow these steps
NX Let's create a new workspace [https://nx.dev/getting-started/intro]
√ Which stack do you want to use? · angular
√ Integrated monorepo, or standalone project? · integrated
√ Application name · fe
√ Which bundler would you like to use? · esbuild
√ Default stylesheet format · scss
√ Do you want to enable Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering)? · Yes
√ Test runner to use for end to end (E2E) tests · playwright
√ Do you want Nx Cloud to make your CI fast? · github
nx s be
> nx run be:serve:development
Build option outputFileName not setfor be. Using fallback value of dist\apps\be\main.js.
> nx run be:build
chunk (runtime: main) main.js (main) 2.71 KiB [entry] [rendered]
webpack compiled successfully (f60f6de829567d37)
———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
NX Successfully ran target build for project be (3s)
Debugger listening on ws://localhost:9229/45b5e4be-970d-449c-ae66-4be0dfa0cf52
Debugger listening on ws://localhost:9229/45b5e4be-970d-449c-ae66-4be0dfa0cf52
For help, see: https://nodejs.org/en/docs/inspector
[Nest] 28260 - 03/04/2024, 11:43:34 PM LOG [NestFactory] Starting Nest application...
[Nest] 28260 - 03/04/2024, 11:43:34 PM LOG [InstanceLoader] AppModule dependencies initialized +5ms
[Nest] 28260 - 03/04/2024, 11:43:34 PM LOG [RoutesResolver] AppController {/api}: +12ms
[Nest] 28260 - 03/04/2024, 11:43:34 PM LOG [RouterExplorer] Mapped {/api, GET} route +1ms
[Nest] 28260 - 03/04/2024, 11:43:34 PM LOG [NestApplication] Nest application successfully started +1ms
[Nest] 28260 - 03/04/2024, 11:43:34 PM LOG 🚀 Application is running on: http://localhost:3000/api
Package Manager Version
No response
Operating System
macOS
Linux
Windows
Other (Please specify)
Additional Information
these are 4 different issues related to multiple issues, if you want me to create separate issues for each or for one of them just tell me and I will do
I'm also open to contribute to fix these issues, just let's agree how they should work and point me to where to go to fix them because I get lost easily in the repo
The text was updated successfully, but these errors were encountered:
❌ > nx run gateway-e2e:test
Setting up...
FAIL gateway-e2e src/gateway/gateway.spec.ts
GET /api
✕ should return a message (39 ms)
● GET /api › should return a message
AggregateError
at Function.Object.<anonymous>.AxiosError.from (../../node_modules/.pnpm/axios@1.6.7/node_modules/axios/lib/core/AxiosError.js:89:14)
at RedirectableRequest.handleRequestError (../../node_modules/.pnpm/axios@1.6.7/node_modules/axios/lib/adapters/http.js:610:25)
at ClientRequest.eventHandlers.<computed> (../../node_modules/.pnpm/follow-redirects@1.15.5/node_modules/follow-redirects/index.js:38:24)
at Axios.request (../../node_modules/.pnpm/axios@1.6.7/node_modules/axios/lib/core/Axios.js:45:[41](https://github.com/safe-health/platform/actions/runs/8180154723/job/22367616715#step:8:46))
Cause:
AggregateError
Current Behavior
right now when I create a new project using angular then add nest to do there are multiple problems
fatal: ambiguous argument 'origin/main': unknown revision or path not in the working tree.
that's because the branch that nx created is
master
but the default branch innrwl/nx-set-shas
jon ismain
Executable doesn't exist at /home/runner/.cache/ms-playwright/chromium-1105/chrome-linux/chrome
nx run-many -t serve
doesn't work, only the first one actually is served and it's random sometimes it's Angular and some other it's nestExpected Behavior
main-branch-name
for master in the.github/workflows/ci.yml
file like what I did here robertIsaac/ng-nest-reprod@527b401npx playwright install --with-deps
as I did in robertIsaac/ng-nest-reprod@a8b0207 or to add it as an extra step in theci.yaml
fileGitHub Repo
https://github.com/robertIsaac/ng-nest-reprod
Steps to Reproduce
1.create a new project
npx create-nx-workspace ng-nest-reprod
then follow these stepsnx add @nx/nest
nx g @nx/nest:app be --frontendProject fe
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
these are 4 different issues related to multiple issues, if you want me to create separate issues for each or for one of them just tell me and I will do
I'm also open to contribute to fix these issues, just let's agree how they should work and point me to where to go to fix them because I get lost easily in the repo
The text was updated successfully, but these errors were encountered: