X Tutup
The Wayback Machine - https://web.archive.org/web/20190625220210/https://github.com/angular/angular-cli/issues/11213
Skip to content
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

Add style include paths for angular6 libraries (ng-packagr) #11213

Closed
totkeks opened this issue Jun 12, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@totkeks
Copy link

commented Jun 12, 2018

- [ ] bug report -> please search issues before submitting
- [x] feature request

Area

- [x] devkit/build-ng-packagr

Versions

Angular CLI: 6.0.8
Node: 8.11.2
OS: win32 x64
Angular: 6.0.4
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.6.8
@angular-devkit/build-angular      0.6.8
@angular-devkit/build-ng-packagr   0.6.8
@angular-devkit/build-optimizer    0.6.8
@angular-devkit/build-webpack      0.7.0-beta.2
@angular-devkit/core               0.6.8
@angular-devkit/schematics         0.6.8
@angular/cli                       6.0.8
@ngtools/json-schema               1.1.0
@ngtools/webpack                   6.0.8
@schematics/angular                0.6.8
@schematics/update                 0.6.8
ng-packagr                         3.0.1
rxjs                               6.2.0
typescript                         2.7.2
webpack                            4.8.3

Desired functionality

  • enable the configuration option "stylePreprocessorOptions" for the library build or use the settings from the default project (not the best idea I guess)

Workaround

@filipesilva

This comment has been minimized.

Copy link
Member

commented Jun 13, 2018

We definitely don't want to assume the settings from another app in this case. The currently behaviour is ideal we feel, where each project defines its own build settings. The file where build options for ng-packagr are defined is ng-package.json.

@totkeks

This comment has been minimized.

Copy link
Author

commented Jun 13, 2018

Thanks for the explanation, I can understand that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
X Tutup