Skip to content

Eject to custom webpack configuration file #6731

Closed

Description

@bampakoa

Bug Report or Feature Request (mark with an x)

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

Versions.

@angular/cli: 1.1.2 (e)
node: 6.9.5
os: win32 x64
@angular/common: 4.2.3
@angular/compiler: 4.2.3
@angular/core: 4.2.3
@angular/forms: 4.2.3
@angular/http: 4.2.3
@angular/platform-browser: 4.2.3
@angular/platform-browser-dynamic: 4.2.3
@angular/router: 4.2.3
@angular/cli: 1.1.2
@angular/compiler-cli: 4.2.3

Repro steps.

The log given by the failure.

Desired functionality.

I maintain different webpack configuration files for the needs of my project (2 for development and 2 for production). One of the development files is the default webpack.config.js which I use to merge changes back to the remaining ones, when a new version of CLI is released. That is, I run ng eject each time to apply the changes in the default config, inspect those changes and apply them to the other files by hand. I follow this process in order not to mess up my custom configuration in the webpack configuration files. It would be really handy, if I could define the target config file of the eject command such as: ng eject --config=<the config file> and have the changes directly applied to the configuration files.

Mention any other details that might be useful.

Activity

  1. self-assigned this
    on Jun 19, 2017
  2. added
    P5The team acknowledges the request but does not plan to address it, it remains open for discussion
    featureLabel used to distinguish feature request from other issues
    on Jun 19, 2017
  3. clydin commented on Sep 28, 2018

    @clydin
    Member

    eject functionality is no longer available in the latest version (6.x+). For custom webpack configurations the following unofficial add-on is a suggested solution: https://github.com/manfredsteyer/ngx-build-plus

  4. angular-automatic-lock-bot commented on Sep 8, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  5. locked and limited conversation to collaborators on Sep 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P5The team acknowledges the request but does not plan to address it, it remains open for discussionfeatureLabel used to distinguish feature request from other issuesseverity2: inconvenient

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions