[Feature]: @puppeteer/ng-schematics:builder should support setting tsconfig.json, using path aliases, replacing environment.ts and not starting the dev-server

[pfeileon]

Feature description

• Right now the path to the tsconfig.json is hard-coded to e2e/tsconfig.json and cannot be set via "options": { "tsconfig": "path/to/tsconfig.json" } which forces you to use the same folder structure and the same filename (I personally would prefer to rename the config to tsconfig.e2e.json).

• TS path aliases are not replaced right now, so you cannot use an import like import { environment } from '@env/environment.ci'.

• Replacing the environment.ts file isn't working, nothing is replaced. This makes it awkward to use ng e2e locally and in a CI environment. Normally you'd call something like npm run e2e:ci in your pipeline which would run ng e2e --configuration ci and locally you'd simply run npm run e2e/ng e2e.

• It's impossible to run ng e2e in a CI environment without also pointlessly starting the dev-server.

[Lightning00Blade]

@pfeileon Could you elaborate on the last point

It's impossible to run ng e2e in a CI environment without also pointlessly starting the dev-server.

What's your use case and why do you deem the starting of the server "pointless"?

[pfeileon]

@pfeileon Could you elaborate on the last point

It's impossible to run ng e2e in a CI environment without also pointlessly starting the dev-server.

What's your use case and why do you deem the starting of the server "pointless"?

Sure. :)
When running the e2e tests locally, it's practical to use the dev-server, of course. But when running the tests in a CI environment they should be running against real instances of the app which is why replacing the environment.ts-file is in this feature request as, well. In this case the dev-server is running for no reason because puppeteer is navigating to the staging or production environment, etc. and not to localhost.