Angular-cli: deprication notice while build: Node#moveTo was deprecated. Use Container#append.

[sibiraj-s]

Version

    _                      _                 ____ _     ___
   / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
  / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
 / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
               |___/

Angular CLI: 1.5.3
Node: 8.9.1
OS: linux x64
Angular: 5.0.0
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.5.3
@angular/tsc-wrapped: 4.4.6
@angular-devkit/build-optimizer: 0.0.32
@angular-devkit/core: 0.0.20
@angular-devkit/schematics: 0.0.35
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.8.3
@schematics/angular: 0.1.0
typescript: 2.4.2
webpack: 3.8.1

Observed behavior

30% building modules 167/168 modules 1 active ...nts/src/styles.scssNode#moveTo was deprecated. Use Container#append.

After updating to 1.5.3 I get this notice with scss while running ng build --prod

[filipesilva]

Heya, I tried this on a new project with this src/styles.scss:

body {
  background-color: #000000
}

But couldn't see that message.

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?

You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

I guess it's related to some dependency update but there might be more to it.

[clydin]

This is coming from cssnano. It still uses some deprecated methods. The methods still function and the warning will only be shown at most once. The next version of cssnano (when released) should completely resolve the issue.

[sibiraj-s]

Can you setup a minimal repro please?

sure @filipesilva.

[sibiraj-s]

@filipesilva .

Steps to Reproduce.

This is what I did. I set default stylesheets to scss

1. ng new myApp
2. npm install bootstrap@next
3. import bootstrap.scss into style.scss

/* You can add global styles to this file, and also import other style files */

@import "../node_modules/bootstrap/scss/bootstrap"; // I used bootstrap

1. ng build -- prod

The problem occurs while importing files into styles.scss

myApp.zip

[gpit2286]

Some issue when trying to import normalize.css.

Same setup. SCSS, @import, etc.

[dragonflypl]

Same issue here after migration to 1.6.0: Build stderr: Node#moveTo was deprecated. Use Container#append.

"styles": [
        "path-to-bootstrap4-sass-here"
      ],

Looks like first version that has this error is 1.5.3 and it throws this error only in --prod mode.

[Dok11]

I have same trouble with bootstrap 4 file _normalize.scss for rule:

b,
strong {
  font-weight: inherit;
}

but without b all is fine:

[skorunka]

Same problem, cli 1.6.3

[fusionx86]

I'm having problems with this too and it's causing TeamCity builds to fail that are otherwise clean. I haven't found a good workaround for this, but the real problem is non-error messages being sent to STDERR. When we will have the ability to filter non-error messages? Even better would be to stop sending everything to the wrong output. Not sure how this behavior is acceptable...

[johnlacr]

Most likely the node.js deprecate method in the util method is being used - this is documented to write to STDERR: https://nodejs.org/api/util.html#util_util_deprecate_function_string

[polyglotinc]

same problem with cli 1.6.6

[Londovir]

This one is getting frustrating on our TFS/MSBuild chains because it throws a "partial success" (or partial fail, depending on your viewpoint), which makes it look like our build is faulty. I've tried using variations on the --no-deprecation flag for Node, but no way of launching my scripts seems to make that flag work to hide the deprecation alert. I've even tried editing an ejected webpack.config.js file to include a process.noDeprecation = true; line, but that doesn't work either. Is there no way to get around the spurious deprecation warning until 1.7.0 comes out someday?

[ubarevicius]

I'm experiencing the same problem, spent an hour to try and silence this on our build server with no luck. cli v1.6.5. I don't see it on cli 1.7.0 beta 2, but ng serve still crashes our application, so can't use it on dev environment. If it doesn't appear on 1.7, would be nice to have the fix on 1.6.7

[denny89k]

so which version of angular/cli does work for angular 5 ng build --prod ?

[imgregduh]

Angular 4

I am having this problem only with ng build --prod also

@Londovir Concerning TFS build definitions, I had to toggle ContinueOnErroroption under control options inside the task. Downside to this, it will continue on ANY error though it will be recorded in the logs that it had errors. I would think you run your application locally first before deploying, so build commands shouldn't usually have a problem. This is only a bandaid and like all injuries if you bleed a lot 1 bandaid wont be enough
ref: msdn

[ubarevicius]

1.7.0-beta.3 release of the cli works fine for us, the error is gone and now it doesn't crash anymore at runtime while serving aot compiled websites.

[Londovir]

I may have to hold until 1.7.0 launches officially. Our team usually uses CLI in an ejected format, since we have custom tooling we need to add to the build chain, so in cases like this I'll need to use the CLI to create a shell project, eject it so I can see how they've changed the base webpack config files (likely removing cssnano since I believe that is the source of the deprecated "error"), and then update our customized webpack configs as needed.

[jfernandeze]

I'have the same issue

"@angular/cli": "1.6.6",
"bootstrap": "~4.0.0",

Version of node: 8.9.4

ng build --prod rcassetsstylesstyle.scssNode#moveTo was Date: 2018-02-02T07:52:15.646Z 45% building modules 296/297 modules 1 active ...sWebSpasrcassetsstylesstyle.scssNode#moveTo was Date: 2018-02-02T07:52:15.646Z

[thovo]

Hi everyone, I had the same problem with cli 1.6.7, is there any update how to fix this?

[Baklap4]

Same here with cli 1.6.8 running on node 9.4.0

[manolosky]

Same here:

Angular CLI: 1.6.8
Node: 8.9.0
OS: darwin x64
Angular: 5.2.5

"bootstrap": "4.0.0-beta.2"

I need help...

[sibiraj-s]

@manolosky . Update angular-cli to v1.7.0.

[Sathishchary]

I am getting same issue after converting from angular 4.3.1 to 5.2.5.

[rag7s]

C:xampphtdocsprofile>ng build --prod
10% building modules 5/5 modules 0 activeNode#moveTo was deprecated. Use Container#append.
Getting above issue please help me with this.

[dojchek]

Guys, you should just upgrade angular-cli to 1.7.0+ and the warning will be gone.

[Baklap4]

Can confirm this running 1.7.2 and it disappeared

[rag7s]

I found the solution for this '0% building modules 5/5 modules 0 activeNode#moveTo was deprecated. Use Container#append.'
Example: if css has classes like this .container{color:red;} .container{font-size:14px;} then you will get this error means douplicate classes.
It should be .container{color:red;font-size:14px;} then it wont show this error.

Like this I checked enter my project and then fixed this error.

[vehansayvazi]

updated to 1.7.2 and it's fixed

[ashkaushik]

updated angular/cli to 1.7.3 and its working fine

[Adrian1907]

updated angular/cli to 1.7.4 and its working fine :)

[angular-automatic-lock-bot[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._}