How do I add an additional postcss plugin via the new @angular/cli v7 angular.json or...












1














@angular/cli@7+ allows a customWebpackConfig to be specified to provide custom webpack configuration, such as:



  "architect": {
"build": {
"builder": "@angular-builders/custom-webpack:browser",
"options": {
"customWebpackConfig": {
"path": "./build/custom-webpack.config.js",
"mergeStrategies": {
"externals": "prepend"
}
},
...


This file then technically allows you to prepend, append or replace any portion of the webpack configuration. Prior to upgrading to @angular@7.1.3 and @angular/cli@7.1.3 we had ejected the webpack configuration to make some additions. One such addition was the postcss-momentum-scrolling postcss-loader plugin that automatically enabled iOS momentum scrolling on all scrollable containers.



I am seeking support on figuring out how to generate the necessary custom webpack code to load this plugin via the supported customizations allowed by @angular/cli@7+.



Here is a sample of what I have tried in my custom-webpack.config.js file:



const postcssMomentumScrolling = require('postcss-momentum-scrolling');

module.exports = {
module: {
rules: [
{
test: /.scss$|.sass$/,
use: [
{
"loader": "postcss-loader",
"options": {
"plugins": [
postcssMomentumScrolling(),
]
}
}
]
},
],
},
};


As soon as I touch the scss chunk of the webpack config, it seems to do a replace instead of a merge or prepend, breaking the build.



I am wondering if anyone has a guide or suggestions on how to see what the initial webpack configuration that @angular/cli generates that is the starting point for modifications and a way to preview/peek at the code to be executed as debugging.



Also, an example of a similar customization would be great.



Thanks!










share|improve this question



























    1














    @angular/cli@7+ allows a customWebpackConfig to be specified to provide custom webpack configuration, such as:



      "architect": {
    "build": {
    "builder": "@angular-builders/custom-webpack:browser",
    "options": {
    "customWebpackConfig": {
    "path": "./build/custom-webpack.config.js",
    "mergeStrategies": {
    "externals": "prepend"
    }
    },
    ...


    This file then technically allows you to prepend, append or replace any portion of the webpack configuration. Prior to upgrading to @angular@7.1.3 and @angular/cli@7.1.3 we had ejected the webpack configuration to make some additions. One such addition was the postcss-momentum-scrolling postcss-loader plugin that automatically enabled iOS momentum scrolling on all scrollable containers.



    I am seeking support on figuring out how to generate the necessary custom webpack code to load this plugin via the supported customizations allowed by @angular/cli@7+.



    Here is a sample of what I have tried in my custom-webpack.config.js file:



    const postcssMomentumScrolling = require('postcss-momentum-scrolling');

    module.exports = {
    module: {
    rules: [
    {
    test: /.scss$|.sass$/,
    use: [
    {
    "loader": "postcss-loader",
    "options": {
    "plugins": [
    postcssMomentumScrolling(),
    ]
    }
    }
    ]
    },
    ],
    },
    };


    As soon as I touch the scss chunk of the webpack config, it seems to do a replace instead of a merge or prepend, breaking the build.



    I am wondering if anyone has a guide or suggestions on how to see what the initial webpack configuration that @angular/cli generates that is the starting point for modifications and a way to preview/peek at the code to be executed as debugging.



    Also, an example of a similar customization would be great.



    Thanks!










    share|improve this question

























      1












      1








      1







      @angular/cli@7+ allows a customWebpackConfig to be specified to provide custom webpack configuration, such as:



        "architect": {
      "build": {
      "builder": "@angular-builders/custom-webpack:browser",
      "options": {
      "customWebpackConfig": {
      "path": "./build/custom-webpack.config.js",
      "mergeStrategies": {
      "externals": "prepend"
      }
      },
      ...


      This file then technically allows you to prepend, append or replace any portion of the webpack configuration. Prior to upgrading to @angular@7.1.3 and @angular/cli@7.1.3 we had ejected the webpack configuration to make some additions. One such addition was the postcss-momentum-scrolling postcss-loader plugin that automatically enabled iOS momentum scrolling on all scrollable containers.



      I am seeking support on figuring out how to generate the necessary custom webpack code to load this plugin via the supported customizations allowed by @angular/cli@7+.



      Here is a sample of what I have tried in my custom-webpack.config.js file:



      const postcssMomentumScrolling = require('postcss-momentum-scrolling');

      module.exports = {
      module: {
      rules: [
      {
      test: /.scss$|.sass$/,
      use: [
      {
      "loader": "postcss-loader",
      "options": {
      "plugins": [
      postcssMomentumScrolling(),
      ]
      }
      }
      ]
      },
      ],
      },
      };


      As soon as I touch the scss chunk of the webpack config, it seems to do a replace instead of a merge or prepend, breaking the build.



      I am wondering if anyone has a guide or suggestions on how to see what the initial webpack configuration that @angular/cli generates that is the starting point for modifications and a way to preview/peek at the code to be executed as debugging.



      Also, an example of a similar customization would be great.



      Thanks!










      share|improve this question













      @angular/cli@7+ allows a customWebpackConfig to be specified to provide custom webpack configuration, such as:



        "architect": {
      "build": {
      "builder": "@angular-builders/custom-webpack:browser",
      "options": {
      "customWebpackConfig": {
      "path": "./build/custom-webpack.config.js",
      "mergeStrategies": {
      "externals": "prepend"
      }
      },
      ...


      This file then technically allows you to prepend, append or replace any portion of the webpack configuration. Prior to upgrading to @angular@7.1.3 and @angular/cli@7.1.3 we had ejected the webpack configuration to make some additions. One such addition was the postcss-momentum-scrolling postcss-loader plugin that automatically enabled iOS momentum scrolling on all scrollable containers.



      I am seeking support on figuring out how to generate the necessary custom webpack code to load this plugin via the supported customizations allowed by @angular/cli@7+.



      Here is a sample of what I have tried in my custom-webpack.config.js file:



      const postcssMomentumScrolling = require('postcss-momentum-scrolling');

      module.exports = {
      module: {
      rules: [
      {
      test: /.scss$|.sass$/,
      use: [
      {
      "loader": "postcss-loader",
      "options": {
      "plugins": [
      postcssMomentumScrolling(),
      ]
      }
      }
      ]
      },
      ],
      },
      };


      As soon as I touch the scss chunk of the webpack config, it seems to do a replace instead of a merge or prepend, breaking the build.



      I am wondering if anyone has a guide or suggestions on how to see what the initial webpack configuration that @angular/cli generates that is the starting point for modifications and a way to preview/peek at the code to be executed as debugging.



      Also, an example of a similar customization would be great.



      Thanks!







      angular7 postcss-loader angular-cli-v7






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 28 '18 at 7:31









      MichaelMichael

      61




      61
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53955119%2fhow-do-i-add-an-additional-postcss-plugin-via-the-new-angular-cli-v7-angular-js%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53955119%2fhow-do-i-add-an-additional-postcss-plugin-via-the-new-angular-cli-v7-angular-js%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Mossoró

          Error while reading .h5 file using the rhdf5 package in R

          Pushsharp Apns notification error: 'InvalidToken'