Trace: The node type SpreadProperty has been renamed to SpreadElement at Object.isSpreadProperty












8















I'm launching a react app, and here's my Webpack configuration:



'use strict'

const ExtractPlugin = require('extract-text-webpack-plugin')
const HTMLPlugin = require('html-webpack-plugin')
module.exports = {
devtool: 'eval',
entry: `${__dirname}/src/main.js`,
output: {
filename: 'bundle-[hash].js',
path: `${__dirname}/build`,
publicPath: '/',
},
mode: 'development',
performance: {
hints: false
},
plugins: [
new HTMLPlugin(),
new ExtractPlugin('bundle-[hash].css'),
],
module: {
rules: [
{
test: /.js$/,
exclude: /node_module/,
loader: 'babel-loader',
},
{
test: /.scss$/,
loader: ExtractPlugin.extract(['css-loader', 'sass-loader']),
},
],
},
}


Then, I have a package.json file, here are the dependencies:



"devDependencies": {
"@babel/core": "^7.1.6",
"@babel/plugin-proposal-object-rest-spread": "^7.0.0",
"@babel/preset-env": "^7.1.6",
"@babel/preset-react": "^7.0.0",
"and": "0.0.3",
"babel-cli": "^6.26.0",
"babel-core": "^7.0.0-bridge.0",
"babel-loader": "^8.0.4",
"eslint": "^5.9.0",
"install": "^0.12.2",
"jest": "^23.6.0",
"npm": "^6.4.1",
"webpack-cli": "^3.1.2"
},
"dependencies": {
"babel-plugin-transform-object-rest-spread": "^6.26.0",
"babel-plugin-transform-runtime": "^6.23.0",
"babel-preset-env": "^1.7.0",
"css-loader": "^1.0.1",
"extract-text-webpack-plugin": "^4.0.0-beta.0",
"html-webpack-plugin": "^3.2.0",
"node-sass": "^4.11.0",
"react": "^16.6.3",
"react-dom": "^16.6.3",
"resolve-url-loader": "^3.0.0",
"sass-loader": "^7.1.0",
"webpack": "^4.25.1",
"webpack-dev-server": "^3.1.10"
}


I have tried plenty of ways of updating babel packages up to 7th version, changing babelrc config, what ever.



The project though compiles, but in the beginning of compilation I get the following message:



Trace: The node type SpreadProperty has been renamed to SpreadElement
at Object.isSpreadProperty



And about of hundred rows like that. After all that rows being printed out, the compilation process proceeds and is completed successfully.



What's that and how can I get rid of this rows?










share|improve this question



























    8















    I'm launching a react app, and here's my Webpack configuration:



    'use strict'

    const ExtractPlugin = require('extract-text-webpack-plugin')
    const HTMLPlugin = require('html-webpack-plugin')
    module.exports = {
    devtool: 'eval',
    entry: `${__dirname}/src/main.js`,
    output: {
    filename: 'bundle-[hash].js',
    path: `${__dirname}/build`,
    publicPath: '/',
    },
    mode: 'development',
    performance: {
    hints: false
    },
    plugins: [
    new HTMLPlugin(),
    new ExtractPlugin('bundle-[hash].css'),
    ],
    module: {
    rules: [
    {
    test: /.js$/,
    exclude: /node_module/,
    loader: 'babel-loader',
    },
    {
    test: /.scss$/,
    loader: ExtractPlugin.extract(['css-loader', 'sass-loader']),
    },
    ],
    },
    }


    Then, I have a package.json file, here are the dependencies:



    "devDependencies": {
    "@babel/core": "^7.1.6",
    "@babel/plugin-proposal-object-rest-spread": "^7.0.0",
    "@babel/preset-env": "^7.1.6",
    "@babel/preset-react": "^7.0.0",
    "and": "0.0.3",
    "babel-cli": "^6.26.0",
    "babel-core": "^7.0.0-bridge.0",
    "babel-loader": "^8.0.4",
    "eslint": "^5.9.0",
    "install": "^0.12.2",
    "jest": "^23.6.0",
    "npm": "^6.4.1",
    "webpack-cli": "^3.1.2"
    },
    "dependencies": {
    "babel-plugin-transform-object-rest-spread": "^6.26.0",
    "babel-plugin-transform-runtime": "^6.23.0",
    "babel-preset-env": "^1.7.0",
    "css-loader": "^1.0.1",
    "extract-text-webpack-plugin": "^4.0.0-beta.0",
    "html-webpack-plugin": "^3.2.0",
    "node-sass": "^4.11.0",
    "react": "^16.6.3",
    "react-dom": "^16.6.3",
    "resolve-url-loader": "^3.0.0",
    "sass-loader": "^7.1.0",
    "webpack": "^4.25.1",
    "webpack-dev-server": "^3.1.10"
    }


    I have tried plenty of ways of updating babel packages up to 7th version, changing babelrc config, what ever.



    The project though compiles, but in the beginning of compilation I get the following message:



    Trace: The node type SpreadProperty has been renamed to SpreadElement
    at Object.isSpreadProperty



    And about of hundred rows like that. After all that rows being printed out, the compilation process proceeds and is completed successfully.



    What's that and how can I get rid of this rows?










    share|improve this question

























      8












      8








      8








      I'm launching a react app, and here's my Webpack configuration:



      'use strict'

      const ExtractPlugin = require('extract-text-webpack-plugin')
      const HTMLPlugin = require('html-webpack-plugin')
      module.exports = {
      devtool: 'eval',
      entry: `${__dirname}/src/main.js`,
      output: {
      filename: 'bundle-[hash].js',
      path: `${__dirname}/build`,
      publicPath: '/',
      },
      mode: 'development',
      performance: {
      hints: false
      },
      plugins: [
      new HTMLPlugin(),
      new ExtractPlugin('bundle-[hash].css'),
      ],
      module: {
      rules: [
      {
      test: /.js$/,
      exclude: /node_module/,
      loader: 'babel-loader',
      },
      {
      test: /.scss$/,
      loader: ExtractPlugin.extract(['css-loader', 'sass-loader']),
      },
      ],
      },
      }


      Then, I have a package.json file, here are the dependencies:



      "devDependencies": {
      "@babel/core": "^7.1.6",
      "@babel/plugin-proposal-object-rest-spread": "^7.0.0",
      "@babel/preset-env": "^7.1.6",
      "@babel/preset-react": "^7.0.0",
      "and": "0.0.3",
      "babel-cli": "^6.26.0",
      "babel-core": "^7.0.0-bridge.0",
      "babel-loader": "^8.0.4",
      "eslint": "^5.9.0",
      "install": "^0.12.2",
      "jest": "^23.6.0",
      "npm": "^6.4.1",
      "webpack-cli": "^3.1.2"
      },
      "dependencies": {
      "babel-plugin-transform-object-rest-spread": "^6.26.0",
      "babel-plugin-transform-runtime": "^6.23.0",
      "babel-preset-env": "^1.7.0",
      "css-loader": "^1.0.1",
      "extract-text-webpack-plugin": "^4.0.0-beta.0",
      "html-webpack-plugin": "^3.2.0",
      "node-sass": "^4.11.0",
      "react": "^16.6.3",
      "react-dom": "^16.6.3",
      "resolve-url-loader": "^3.0.0",
      "sass-loader": "^7.1.0",
      "webpack": "^4.25.1",
      "webpack-dev-server": "^3.1.10"
      }


      I have tried plenty of ways of updating babel packages up to 7th version, changing babelrc config, what ever.



      The project though compiles, but in the beginning of compilation I get the following message:



      Trace: The node type SpreadProperty has been renamed to SpreadElement
      at Object.isSpreadProperty



      And about of hundred rows like that. After all that rows being printed out, the compilation process proceeds and is completed successfully.



      What's that and how can I get rid of this rows?










      share|improve this question














      I'm launching a react app, and here's my Webpack configuration:



      'use strict'

      const ExtractPlugin = require('extract-text-webpack-plugin')
      const HTMLPlugin = require('html-webpack-plugin')
      module.exports = {
      devtool: 'eval',
      entry: `${__dirname}/src/main.js`,
      output: {
      filename: 'bundle-[hash].js',
      path: `${__dirname}/build`,
      publicPath: '/',
      },
      mode: 'development',
      performance: {
      hints: false
      },
      plugins: [
      new HTMLPlugin(),
      new ExtractPlugin('bundle-[hash].css'),
      ],
      module: {
      rules: [
      {
      test: /.js$/,
      exclude: /node_module/,
      loader: 'babel-loader',
      },
      {
      test: /.scss$/,
      loader: ExtractPlugin.extract(['css-loader', 'sass-loader']),
      },
      ],
      },
      }


      Then, I have a package.json file, here are the dependencies:



      "devDependencies": {
      "@babel/core": "^7.1.6",
      "@babel/plugin-proposal-object-rest-spread": "^7.0.0",
      "@babel/preset-env": "^7.1.6",
      "@babel/preset-react": "^7.0.0",
      "and": "0.0.3",
      "babel-cli": "^6.26.0",
      "babel-core": "^7.0.0-bridge.0",
      "babel-loader": "^8.0.4",
      "eslint": "^5.9.0",
      "install": "^0.12.2",
      "jest": "^23.6.0",
      "npm": "^6.4.1",
      "webpack-cli": "^3.1.2"
      },
      "dependencies": {
      "babel-plugin-transform-object-rest-spread": "^6.26.0",
      "babel-plugin-transform-runtime": "^6.23.0",
      "babel-preset-env": "^1.7.0",
      "css-loader": "^1.0.1",
      "extract-text-webpack-plugin": "^4.0.0-beta.0",
      "html-webpack-plugin": "^3.2.0",
      "node-sass": "^4.11.0",
      "react": "^16.6.3",
      "react-dom": "^16.6.3",
      "resolve-url-loader": "^3.0.0",
      "sass-loader": "^7.1.0",
      "webpack": "^4.25.1",
      "webpack-dev-server": "^3.1.10"
      }


      I have tried plenty of ways of updating babel packages up to 7th version, changing babelrc config, what ever.



      The project though compiles, but in the beginning of compilation I get the following message:



      Trace: The node type SpreadProperty has been renamed to SpreadElement
      at Object.isSpreadProperty



      And about of hundred rows like that. After all that rows being printed out, the compilation process proceeds and is completed successfully.



      What's that and how can I get rid of this rows?







      reactjs webpack babel






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 15 '18 at 19:52









      Dominik DomanskiDominik Domanski

      111211




      111211
























          3 Answers
          3






          active

          oldest

          votes


















          1














          In my case, I was not implementing the Webpack configuration and still error was there. After so many solutions implementation, the error was same or once an error was removed another appeared. Finally, I deleted .bablerc, .babelrc and package-lock.json files and ran rm -rf node_modules && npm install and then ran react-native run-android and it worked for me. :-)






          share|improve this answer
























          • I believe the problem comes from using babel-preset-react-native, which depends on /babel-plugin-transform-object-rest-spread (an older version of @babel/plugin-proposal-object-rest-spread). Rather than deleting the entire .babelrc, you should be able to just remove react-native from the presets.

            – Chris Bobbe
            Mar 14 at 15:32



















          11














          here is the final setting that solved problem for me.



          .babelrc



          {
          "presets": [
          "@babel/preset-env",
          "@babel/preset-react"
          ],
          "plugins": [
          "@babel/plugin-proposal-object-rest-spread"
          ]
          }


          For a better understanding, here is my package.json's devDependencies:



          "devDependencies": {
          "@babel/core": "^7.1.6",
          "@babel/plugin-proposal-object-rest-spread": "^7.0.0",
          "@babel/plugin-transform-object-assign": "^7.0.0",
          "@babel/plugin-transform-react-jsx": "^7.1.6",
          "@babel/preset-env": "^7.1.6",
          "@babel/preset-react": "^7.0.0",
          "babel-loader": "8.0.4",
          "prop-types": "15.6.2",
          "react": "^16.6.3",
          "react-dom": "^16.6.3",
          "style-loader": "^0.23.1",
          "utils": "^0.3.1",
          "webpack": "4.26.1",
          "webpack-cli": "3.1.2",
          "webpack-dev-server": "^3.1.10"
          }


          Here is my webpack.config.js module's section:



          module: {
          rules: [
          {
          test: /.(js|jsx)$/ ,
          exclude: /node_modules/,
          loaders: "babel-loader"
          }
          ]
          }





          share|improve this answer
























          • not sure how this is not the accepted answer but this should have been it, I had updated to babel 7 but had not yet used the proper updated plugins

            – eballeste
            Jan 30 at 22:38



















          7














          Here's the similar problem was resolved






          share|improve this answer



















          • 2





            Can you put the solution inline?

            – benc
            Nov 16 '18 at 3:12






          • 3





            I ran npm install --save-dev @babel/plugin-proposal-object-rest-spread, then changed my babelrc to { "presets": [ "@babel/preset-env", "@babel/preset-react" ], "plugins": ["@babel/plugin-proposal-object-rest-spread"] }

            – Dominik Domanski
            Nov 16 '18 at 6:13











          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%2f53326986%2ftrace-the-node-type-spreadproperty-has-been-renamed-to-spreadelement-at-object%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          3 Answers
          3






          active

          oldest

          votes








          3 Answers
          3






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          In my case, I was not implementing the Webpack configuration and still error was there. After so many solutions implementation, the error was same or once an error was removed another appeared. Finally, I deleted .bablerc, .babelrc and package-lock.json files and ran rm -rf node_modules && npm install and then ran react-native run-android and it worked for me. :-)






          share|improve this answer
























          • I believe the problem comes from using babel-preset-react-native, which depends on /babel-plugin-transform-object-rest-spread (an older version of @babel/plugin-proposal-object-rest-spread). Rather than deleting the entire .babelrc, you should be able to just remove react-native from the presets.

            – Chris Bobbe
            Mar 14 at 15:32
















          1














          In my case, I was not implementing the Webpack configuration and still error was there. After so many solutions implementation, the error was same or once an error was removed another appeared. Finally, I deleted .bablerc, .babelrc and package-lock.json files and ran rm -rf node_modules && npm install and then ran react-native run-android and it worked for me. :-)






          share|improve this answer
























          • I believe the problem comes from using babel-preset-react-native, which depends on /babel-plugin-transform-object-rest-spread (an older version of @babel/plugin-proposal-object-rest-spread). Rather than deleting the entire .babelrc, you should be able to just remove react-native from the presets.

            – Chris Bobbe
            Mar 14 at 15:32














          1












          1








          1







          In my case, I was not implementing the Webpack configuration and still error was there. After so many solutions implementation, the error was same or once an error was removed another appeared. Finally, I deleted .bablerc, .babelrc and package-lock.json files and ran rm -rf node_modules && npm install and then ran react-native run-android and it worked for me. :-)






          share|improve this answer













          In my case, I was not implementing the Webpack configuration and still error was there. After so many solutions implementation, the error was same or once an error was removed another appeared. Finally, I deleted .bablerc, .babelrc and package-lock.json files and ran rm -rf node_modules && npm install and then ran react-native run-android and it worked for me. :-)







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 5 at 5:00









          UditUdit

          262




          262













          • I believe the problem comes from using babel-preset-react-native, which depends on /babel-plugin-transform-object-rest-spread (an older version of @babel/plugin-proposal-object-rest-spread). Rather than deleting the entire .babelrc, you should be able to just remove react-native from the presets.

            – Chris Bobbe
            Mar 14 at 15:32



















          • I believe the problem comes from using babel-preset-react-native, which depends on /babel-plugin-transform-object-rest-spread (an older version of @babel/plugin-proposal-object-rest-spread). Rather than deleting the entire .babelrc, you should be able to just remove react-native from the presets.

            – Chris Bobbe
            Mar 14 at 15:32

















          I believe the problem comes from using babel-preset-react-native, which depends on /babel-plugin-transform-object-rest-spread (an older version of @babel/plugin-proposal-object-rest-spread). Rather than deleting the entire .babelrc, you should be able to just remove react-native from the presets.

          – Chris Bobbe
          Mar 14 at 15:32





          I believe the problem comes from using babel-preset-react-native, which depends on /babel-plugin-transform-object-rest-spread (an older version of @babel/plugin-proposal-object-rest-spread). Rather than deleting the entire .babelrc, you should be able to just remove react-native from the presets.

          – Chris Bobbe
          Mar 14 at 15:32













          11














          here is the final setting that solved problem for me.



          .babelrc



          {
          "presets": [
          "@babel/preset-env",
          "@babel/preset-react"
          ],
          "plugins": [
          "@babel/plugin-proposal-object-rest-spread"
          ]
          }


          For a better understanding, here is my package.json's devDependencies:



          "devDependencies": {
          "@babel/core": "^7.1.6",
          "@babel/plugin-proposal-object-rest-spread": "^7.0.0",
          "@babel/plugin-transform-object-assign": "^7.0.0",
          "@babel/plugin-transform-react-jsx": "^7.1.6",
          "@babel/preset-env": "^7.1.6",
          "@babel/preset-react": "^7.0.0",
          "babel-loader": "8.0.4",
          "prop-types": "15.6.2",
          "react": "^16.6.3",
          "react-dom": "^16.6.3",
          "style-loader": "^0.23.1",
          "utils": "^0.3.1",
          "webpack": "4.26.1",
          "webpack-cli": "3.1.2",
          "webpack-dev-server": "^3.1.10"
          }


          Here is my webpack.config.js module's section:



          module: {
          rules: [
          {
          test: /.(js|jsx)$/ ,
          exclude: /node_modules/,
          loaders: "babel-loader"
          }
          ]
          }





          share|improve this answer
























          • not sure how this is not the accepted answer but this should have been it, I had updated to babel 7 but had not yet used the proper updated plugins

            – eballeste
            Jan 30 at 22:38
















          11














          here is the final setting that solved problem for me.



          .babelrc



          {
          "presets": [
          "@babel/preset-env",
          "@babel/preset-react"
          ],
          "plugins": [
          "@babel/plugin-proposal-object-rest-spread"
          ]
          }


          For a better understanding, here is my package.json's devDependencies:



          "devDependencies": {
          "@babel/core": "^7.1.6",
          "@babel/plugin-proposal-object-rest-spread": "^7.0.0",
          "@babel/plugin-transform-object-assign": "^7.0.0",
          "@babel/plugin-transform-react-jsx": "^7.1.6",
          "@babel/preset-env": "^7.1.6",
          "@babel/preset-react": "^7.0.0",
          "babel-loader": "8.0.4",
          "prop-types": "15.6.2",
          "react": "^16.6.3",
          "react-dom": "^16.6.3",
          "style-loader": "^0.23.1",
          "utils": "^0.3.1",
          "webpack": "4.26.1",
          "webpack-cli": "3.1.2",
          "webpack-dev-server": "^3.1.10"
          }


          Here is my webpack.config.js module's section:



          module: {
          rules: [
          {
          test: /.(js|jsx)$/ ,
          exclude: /node_modules/,
          loaders: "babel-loader"
          }
          ]
          }





          share|improve this answer
























          • not sure how this is not the accepted answer but this should have been it, I had updated to babel 7 but had not yet used the proper updated plugins

            – eballeste
            Jan 30 at 22:38














          11












          11








          11







          here is the final setting that solved problem for me.



          .babelrc



          {
          "presets": [
          "@babel/preset-env",
          "@babel/preset-react"
          ],
          "plugins": [
          "@babel/plugin-proposal-object-rest-spread"
          ]
          }


          For a better understanding, here is my package.json's devDependencies:



          "devDependencies": {
          "@babel/core": "^7.1.6",
          "@babel/plugin-proposal-object-rest-spread": "^7.0.0",
          "@babel/plugin-transform-object-assign": "^7.0.0",
          "@babel/plugin-transform-react-jsx": "^7.1.6",
          "@babel/preset-env": "^7.1.6",
          "@babel/preset-react": "^7.0.0",
          "babel-loader": "8.0.4",
          "prop-types": "15.6.2",
          "react": "^16.6.3",
          "react-dom": "^16.6.3",
          "style-loader": "^0.23.1",
          "utils": "^0.3.1",
          "webpack": "4.26.1",
          "webpack-cli": "3.1.2",
          "webpack-dev-server": "^3.1.10"
          }


          Here is my webpack.config.js module's section:



          module: {
          rules: [
          {
          test: /.(js|jsx)$/ ,
          exclude: /node_modules/,
          loaders: "babel-loader"
          }
          ]
          }





          share|improve this answer













          here is the final setting that solved problem for me.



          .babelrc



          {
          "presets": [
          "@babel/preset-env",
          "@babel/preset-react"
          ],
          "plugins": [
          "@babel/plugin-proposal-object-rest-spread"
          ]
          }


          For a better understanding, here is my package.json's devDependencies:



          "devDependencies": {
          "@babel/core": "^7.1.6",
          "@babel/plugin-proposal-object-rest-spread": "^7.0.0",
          "@babel/plugin-transform-object-assign": "^7.0.0",
          "@babel/plugin-transform-react-jsx": "^7.1.6",
          "@babel/preset-env": "^7.1.6",
          "@babel/preset-react": "^7.0.0",
          "babel-loader": "8.0.4",
          "prop-types": "15.6.2",
          "react": "^16.6.3",
          "react-dom": "^16.6.3",
          "style-loader": "^0.23.1",
          "utils": "^0.3.1",
          "webpack": "4.26.1",
          "webpack-cli": "3.1.2",
          "webpack-dev-server": "^3.1.10"
          }


          Here is my webpack.config.js module's section:



          module: {
          rules: [
          {
          test: /.(js|jsx)$/ ,
          exclude: /node_modules/,
          loaders: "babel-loader"
          }
          ]
          }






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 28 '18 at 9:22









          Emanuele ColonnelliEmanuele Colonnelli

          1112




          1112













          • not sure how this is not the accepted answer but this should have been it, I had updated to babel 7 but had not yet used the proper updated plugins

            – eballeste
            Jan 30 at 22:38



















          • not sure how this is not the accepted answer but this should have been it, I had updated to babel 7 but had not yet used the proper updated plugins

            – eballeste
            Jan 30 at 22:38

















          not sure how this is not the accepted answer but this should have been it, I had updated to babel 7 but had not yet used the proper updated plugins

          – eballeste
          Jan 30 at 22:38





          not sure how this is not the accepted answer but this should have been it, I had updated to babel 7 but had not yet used the proper updated plugins

          – eballeste
          Jan 30 at 22:38











          7














          Here's the similar problem was resolved






          share|improve this answer



















          • 2





            Can you put the solution inline?

            – benc
            Nov 16 '18 at 3:12






          • 3





            I ran npm install --save-dev @babel/plugin-proposal-object-rest-spread, then changed my babelrc to { "presets": [ "@babel/preset-env", "@babel/preset-react" ], "plugins": ["@babel/plugin-proposal-object-rest-spread"] }

            – Dominik Domanski
            Nov 16 '18 at 6:13
















          7














          Here's the similar problem was resolved






          share|improve this answer



















          • 2





            Can you put the solution inline?

            – benc
            Nov 16 '18 at 3:12






          • 3





            I ran npm install --save-dev @babel/plugin-proposal-object-rest-spread, then changed my babelrc to { "presets": [ "@babel/preset-env", "@babel/preset-react" ], "plugins": ["@babel/plugin-proposal-object-rest-spread"] }

            – Dominik Domanski
            Nov 16 '18 at 6:13














          7












          7








          7







          Here's the similar problem was resolved






          share|improve this answer













          Here's the similar problem was resolved







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 16 '18 at 3:06









          Juddy jsJuddy js

          712




          712








          • 2





            Can you put the solution inline?

            – benc
            Nov 16 '18 at 3:12






          • 3





            I ran npm install --save-dev @babel/plugin-proposal-object-rest-spread, then changed my babelrc to { "presets": [ "@babel/preset-env", "@babel/preset-react" ], "plugins": ["@babel/plugin-proposal-object-rest-spread"] }

            – Dominik Domanski
            Nov 16 '18 at 6:13














          • 2





            Can you put the solution inline?

            – benc
            Nov 16 '18 at 3:12






          • 3





            I ran npm install --save-dev @babel/plugin-proposal-object-rest-spread, then changed my babelrc to { "presets": [ "@babel/preset-env", "@babel/preset-react" ], "plugins": ["@babel/plugin-proposal-object-rest-spread"] }

            – Dominik Domanski
            Nov 16 '18 at 6:13








          2




          2





          Can you put the solution inline?

          – benc
          Nov 16 '18 at 3:12





          Can you put the solution inline?

          – benc
          Nov 16 '18 at 3:12




          3




          3





          I ran npm install --save-dev @babel/plugin-proposal-object-rest-spread, then changed my babelrc to { "presets": [ "@babel/preset-env", "@babel/preset-react" ], "plugins": ["@babel/plugin-proposal-object-rest-spread"] }

          – Dominik Domanski
          Nov 16 '18 at 6:13





          I ran npm install --save-dev @babel/plugin-proposal-object-rest-spread, then changed my babelrc to { "presets": [ "@babel/preset-env", "@babel/preset-react" ], "plugins": ["@babel/plugin-proposal-object-rest-spread"] }

          – Dominik Domanski
          Nov 16 '18 at 6:13


















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53326986%2ftrace-the-node-type-spreadproperty-has-been-renamed-to-spreadelement-at-object%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

          Florida Star v. B. J. F.

          Error while running script in elastic search , gateway timeout

          Adding quotations to stringified JSON object values