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
[Feature]: @puppeteer/ng-schematics:builder
should support setting tsconfig.json, using path aliases, replacing environment.ts and not starting the dev-server
#12222
Comments
@puppeteer/ng-schematics
should support setting tsconfig.json, replacing environment.ts and not starting the dev-server@puppeteer/ng-schematics:builder
should support setting tsconfig.json, using path aliases, replacing environment.ts and not starting the dev-server
@puppeteer/ng-schematics:builder
should support setting tsconfig.json, using path aliases, replacing environment.ts and not starting the dev-server@puppeteer/ng-schematics:builder
should support setting tsconfig.json, using path aliases, replacing environment.ts and not starting the dev-server
@pfeileon Could you elaborate on the last point
What's your use case and why do you deem the starting of the server "pointless"? |
Sure. :) |
Feature description
Right now the path to the
tsconfig.json
is hard-coded toe2e/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 totsconfig.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 useng e2e
locally and in a CI environment. Normally you'd call something likenpm run e2e:ci
in your pipeline which would runng e2e --configuration ci
and locally you'd simply runnpm run e2e
/ng e2e
.It's impossible to run
ng e2e
in a CI environment without also pointlessly starting the dev-server.The text was updated successfully, but these errors were encountered: