-
Notifications
You must be signed in to change notification settings - Fork 23
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
build: implement builders for using with NG CLI #883
Labels
comp: stark-build
Stark Build
Milestone
Comments
this is linked to #114 |
Great! |
Any chance of getting a better integration with Angular CLI in the coming releases? |
Indeed, we'll work on it in the coming weeks so we plan to include it in the first RC 😉 |
3 tasks
This was referenced Feb 13, 2019
Closed
We will use @angular-builders to customize the webpack config to be used with Angular CLI. References: |
christophercr
referenced
this issue
in christophercr/stark
Feb 21, 2019
…r-builders ISSUES CLOSED: #883
christophercr
referenced
this issue
in christophercr/stark
Feb 22, 2019
…r-builders ISSUES CLOSED: #883
3 tasks
christophercr
referenced
this issue
in christophercr/stark
Feb 22, 2019
…r-builders ISSUES CLOSED: #883
christophercr
referenced
this issue
in christophercr/stark
Feb 22, 2019
…r-builders ISSUES CLOSED: #883
christophercr
referenced
this issue
in christophercr/stark
Feb 22, 2019
…r-builders ISSUES CLOSED: #883
christophercr
referenced
this issue
in christophercr/stark
Feb 22, 2019
…r-builders ISSUES CLOSED: #883
christophercr
referenced
this issue
in christophercr/stark
Feb 25, 2019
…r-builders ISSUES CLOSED: #883
christophercr
referenced
this issue
in christophercr/stark
Feb 25, 2019
…r-builders ISSUES CLOSED: #883
christophercr
referenced
this issue
in christophercr/stark
Feb 26, 2019
…r-builders ISSUES CLOSED: #883
christophercr
referenced
this issue
in christophercr/stark
Feb 26, 2019
…r-builders ISSUES CLOSED: #883, #146, 114 BREAKING CHANGE: stark-build now integrates with Angular CLI: - **stark-build:** now provides partial Webpack configurations to override default configuration from Angular CLI. The application's `angular.json` file must be adapted to use this partial configs from stark-build via [@angular-builders](https://github.com/meltedspark/angular-builders). See [Stark-Build: Ng CLI Customizations](./docs/stark-build/NG_CLI_BUILD_CUSTOMIZATIONS.md) - **stark-core:** the application's `angular.json` file must be adapted to add the assets from stark-core to be copied to the application's `assets` folder. See [Stark-Core: Getting Started](./docs/stark-core/GETTING_STARTED.md#assets) - **stark-ui:** the application's `angular.json` file must be adapted to add the assets from stark-ui to be copied to the application's `assets` folder. See [Stark-UI: Getting Started](./docs/stark-ui/GETTING_STARTED.md#assets)
christophercr
referenced
this issue
in christophercr/stark
Feb 26, 2019
…r-builders ISSUES CLOSED: #883, #146, #114 BREAKING CHANGE: stark-build now integrates with Angular CLI: - **stark-build:** now provides partial Webpack configurations to override default configuration from Angular CLI. The application's `angular.json` file must be adapted to use this partial configs from stark-build via [@angular-builders](https://github.com/meltedspark/angular-builders). See [Stark-Build: Ng CLI Customizations](./docs/stark-build/NG_CLI_BUILD_CUSTOMIZATIONS.md) - **stark-core:** the application's `angular.json` file must be adapted to add the assets from stark-core to be copied to the application's `assets` folder. See [Stark-Core: Getting Started](./docs/stark-core/GETTING_STARTED.md#assets) - **stark-ui:** the application's `angular.json` file must be adapted to add the assets from stark-ui to be copied to the application's `assets` folder. See [Stark-UI: Getting Started](./docs/stark-ui/GETTING_STARTED.md#assets)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a...
Current behavior
We use npm scripts to run our application.
Expected behavior
We should use the CLI build and add our customisations thanks to angular builders in stark-build.
What is the motivation / use case for changing the behavior?
Angular team is improving the build system a lot (performance, bundle size, etc.) and we should take advantage of this instead of trying to follow them progressively.
The text was updated successfully, but these errors were encountered: