Babel 7.0 and webpack fail












0














I am trying to run babel



npx webpack -p --env production && babel src --out-dir dist --source-maps inline



As i see the error show up in the later part of the command.



The error that i get after running the command:



Error: Requires Babel "^7.0.0-0", but was loaded with "6.25.0". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel.
at throwVersionError (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:65:11)
at Object.assertVersion (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:13:11)
at _default (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/plugin-proposal-decorators/lib/index.js:35:7)
at /mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:19:12
at Function.memoisePluginContainer (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:113:13)
at Function.normalisePlugin (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:146:32)
at /mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:184:30
at Array.map (<anonymous>)
at Function.normalisePlugins (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
at OptionManager.mergeOptions (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
at OptionManager.init (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
at File.initOptions (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/index.js:212:65)
at new File (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/index.js:135:24)
at Pipeline.transform (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
at transform (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/util.js:50:22)
at Object.compile (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/util.js:59:12)
at write (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:21:21)
at handleFile (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:43:7)
at /mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:61:9
at Array.forEach (<anonymous>)
at handle (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:59:29)
at Array.forEach (<anonymous>)
at module.exports (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:69:15)
at Object.<anonymous> (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/index.js:129:1)
at Module._compile (module.js:662:30)


This is my config.js information:



DevDependencies :



"babel-core": "^7.0.0-bridge.0",
"babel-eslint": "^10.0.1",
"babel-jest": "^23.6.0",
"eslint": "^5.9.0",
"eslint-config-airbnb": "^17.1.0",
"eslint-plugin-flowtype": "^2.50.3",
"eslint-plugin-import": "^2.14.0",
"eslint-plugin-jest": "^21.27.2",
"eslint-plugin-jsx-a11y": "^6.1.2",
"eslint-plugin-react": "^7.11.1",
"flow-bin": "^0.82.0",
"flow-typed": "^2.5.1",
"jest": "^23.6.0",
"jest-cli": "^23.6.0",


Dependencies:



"@babel/cli": "^7.1.5",
"@babel/core": "^7.1.5",
"@babel/node": "^7.0.0",
"@babel/plugin-proposal-class-properties": "^7.1.0",
"@babel/plugin-proposal-decorators": "^7.1.2",
"@babel/polyfill": "^7.0.0",
"@babel/preset-env": "^7.1.5",
"@babel/preset-flow": "^7.0.0",
"@babel/preset-react": "^7.0.0",
"babel-loader": "^8.0.4",
"webpack": "^4.25.1",
"webpack-cli": "^3.1.2"


Webpack config



module: {
rules: [
{
test: /.jsx?$/,
exclude: /node_modules/,
use: 'babel-loader',
},
{
test: /.css$/,
use: ['style-loader', 'css-loader'],
},
],









share|improve this question



























    0














    I am trying to run babel



    npx webpack -p --env production && babel src --out-dir dist --source-maps inline



    As i see the error show up in the later part of the command.



    The error that i get after running the command:



    Error: Requires Babel "^7.0.0-0", but was loaded with "6.25.0". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel.
    at throwVersionError (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:65:11)
    at Object.assertVersion (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:13:11)
    at _default (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/plugin-proposal-decorators/lib/index.js:35:7)
    at /mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:19:12
    at Function.memoisePluginContainer (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:113:13)
    at Function.normalisePlugin (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:146:32)
    at /mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:184:30
    at Array.map (<anonymous>)
    at Function.normalisePlugins (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
    at OptionManager.mergeOptions (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
    at OptionManager.init (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
    at File.initOptions (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/index.js:212:65)
    at new File (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/index.js:135:24)
    at Pipeline.transform (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
    at transform (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/util.js:50:22)
    at Object.compile (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/util.js:59:12)
    at write (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:21:21)
    at handleFile (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:43:7)
    at /mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:61:9
    at Array.forEach (<anonymous>)
    at handle (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:59:29)
    at Array.forEach (<anonymous>)
    at module.exports (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:69:15)
    at Object.<anonymous> (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/index.js:129:1)
    at Module._compile (module.js:662:30)


    This is my config.js information:



    DevDependencies :



    "babel-core": "^7.0.0-bridge.0",
    "babel-eslint": "^10.0.1",
    "babel-jest": "^23.6.0",
    "eslint": "^5.9.0",
    "eslint-config-airbnb": "^17.1.0",
    "eslint-plugin-flowtype": "^2.50.3",
    "eslint-plugin-import": "^2.14.0",
    "eslint-plugin-jest": "^21.27.2",
    "eslint-plugin-jsx-a11y": "^6.1.2",
    "eslint-plugin-react": "^7.11.1",
    "flow-bin": "^0.82.0",
    "flow-typed": "^2.5.1",
    "jest": "^23.6.0",
    "jest-cli": "^23.6.0",


    Dependencies:



    "@babel/cli": "^7.1.5",
    "@babel/core": "^7.1.5",
    "@babel/node": "^7.0.0",
    "@babel/plugin-proposal-class-properties": "^7.1.0",
    "@babel/plugin-proposal-decorators": "^7.1.2",
    "@babel/polyfill": "^7.0.0",
    "@babel/preset-env": "^7.1.5",
    "@babel/preset-flow": "^7.0.0",
    "@babel/preset-react": "^7.0.0",
    "babel-loader": "^8.0.4",
    "webpack": "^4.25.1",
    "webpack-cli": "^3.1.2"


    Webpack config



    module: {
    rules: [
    {
    test: /.jsx?$/,
    exclude: /node_modules/,
    use: 'babel-loader',
    },
    {
    test: /.css$/,
    use: ['style-loader', 'css-loader'],
    },
    ],









    share|improve this question

























      0












      0








      0







      I am trying to run babel



      npx webpack -p --env production && babel src --out-dir dist --source-maps inline



      As i see the error show up in the later part of the command.



      The error that i get after running the command:



      Error: Requires Babel "^7.0.0-0", but was loaded with "6.25.0". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel.
      at throwVersionError (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:65:11)
      at Object.assertVersion (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:13:11)
      at _default (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/plugin-proposal-decorators/lib/index.js:35:7)
      at /mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:19:12
      at Function.memoisePluginContainer (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:113:13)
      at Function.normalisePlugin (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:146:32)
      at /mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:184:30
      at Array.map (<anonymous>)
      at Function.normalisePlugins (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
      at OptionManager.mergeOptions (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
      at OptionManager.init (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
      at File.initOptions (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/index.js:212:65)
      at new File (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/index.js:135:24)
      at Pipeline.transform (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
      at transform (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/util.js:50:22)
      at Object.compile (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/util.js:59:12)
      at write (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:21:21)
      at handleFile (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:43:7)
      at /mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:61:9
      at Array.forEach (<anonymous>)
      at handle (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:59:29)
      at Array.forEach (<anonymous>)
      at module.exports (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:69:15)
      at Object.<anonymous> (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/index.js:129:1)
      at Module._compile (module.js:662:30)


      This is my config.js information:



      DevDependencies :



      "babel-core": "^7.0.0-bridge.0",
      "babel-eslint": "^10.0.1",
      "babel-jest": "^23.6.0",
      "eslint": "^5.9.0",
      "eslint-config-airbnb": "^17.1.0",
      "eslint-plugin-flowtype": "^2.50.3",
      "eslint-plugin-import": "^2.14.0",
      "eslint-plugin-jest": "^21.27.2",
      "eslint-plugin-jsx-a11y": "^6.1.2",
      "eslint-plugin-react": "^7.11.1",
      "flow-bin": "^0.82.0",
      "flow-typed": "^2.5.1",
      "jest": "^23.6.0",
      "jest-cli": "^23.6.0",


      Dependencies:



      "@babel/cli": "^7.1.5",
      "@babel/core": "^7.1.5",
      "@babel/node": "^7.0.0",
      "@babel/plugin-proposal-class-properties": "^7.1.0",
      "@babel/plugin-proposal-decorators": "^7.1.2",
      "@babel/polyfill": "^7.0.0",
      "@babel/preset-env": "^7.1.5",
      "@babel/preset-flow": "^7.0.0",
      "@babel/preset-react": "^7.0.0",
      "babel-loader": "^8.0.4",
      "webpack": "^4.25.1",
      "webpack-cli": "^3.1.2"


      Webpack config



      module: {
      rules: [
      {
      test: /.jsx?$/,
      exclude: /node_modules/,
      use: 'babel-loader',
      },
      {
      test: /.css$/,
      use: ['style-loader', 'css-loader'],
      },
      ],









      share|improve this question













      I am trying to run babel



      npx webpack -p --env production && babel src --out-dir dist --source-maps inline



      As i see the error show up in the later part of the command.



      The error that i get after running the command:



      Error: Requires Babel "^7.0.0-0", but was loaded with "6.25.0". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel.
      at throwVersionError (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:65:11)
      at Object.assertVersion (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:13:11)
      at _default (/mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/plugin-proposal-decorators/lib/index.js:35:7)
      at /mnt/c/Users/Arkadiy/Desktop/project4/node_modules/@babel/helper-plugin-utils/lib/index.js:19:12
      at Function.memoisePluginContainer (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:113:13)
      at Function.normalisePlugin (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:146:32)
      at /mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:184:30
      at Array.map (<anonymous>)
      at Function.normalisePlugins (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
      at OptionManager.mergeOptions (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
      at OptionManager.init (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
      at File.initOptions (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/index.js:212:65)
      at new File (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/file/index.js:135:24)
      at Pipeline.transform (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
      at transform (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/util.js:50:22)
      at Object.compile (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/util.js:59:12)
      at write (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:21:21)
      at handleFile (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:43:7)
      at /mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:61:9
      at Array.forEach (<anonymous>)
      at handle (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:59:29)
      at Array.forEach (<anonymous>)
      at module.exports (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/dir.js:69:15)
      at Object.<anonymous> (/mnt/c/Users/Arkadiy/AppData/Roaming/npm/node_modules/babel-cli/lib/babel/index.js:129:1)
      at Module._compile (module.js:662:30)


      This is my config.js information:



      DevDependencies :



      "babel-core": "^7.0.0-bridge.0",
      "babel-eslint": "^10.0.1",
      "babel-jest": "^23.6.0",
      "eslint": "^5.9.0",
      "eslint-config-airbnb": "^17.1.0",
      "eslint-plugin-flowtype": "^2.50.3",
      "eslint-plugin-import": "^2.14.0",
      "eslint-plugin-jest": "^21.27.2",
      "eslint-plugin-jsx-a11y": "^6.1.2",
      "eslint-plugin-react": "^7.11.1",
      "flow-bin": "^0.82.0",
      "flow-typed": "^2.5.1",
      "jest": "^23.6.0",
      "jest-cli": "^23.6.0",


      Dependencies:



      "@babel/cli": "^7.1.5",
      "@babel/core": "^7.1.5",
      "@babel/node": "^7.0.0",
      "@babel/plugin-proposal-class-properties": "^7.1.0",
      "@babel/plugin-proposal-decorators": "^7.1.2",
      "@babel/polyfill": "^7.0.0",
      "@babel/preset-env": "^7.1.5",
      "@babel/preset-flow": "^7.0.0",
      "@babel/preset-react": "^7.0.0",
      "babel-loader": "^8.0.4",
      "webpack": "^4.25.1",
      "webpack-cli": "^3.1.2"


      Webpack config



      module: {
      rules: [
      {
      test: /.jsx?$/,
      exclude: /node_modules/,
      use: 'babel-loader',
      },
      {
      test: /.css$/,
      use: ['style-loader', 'css-loader'],
      },
      ],






      webpack babel babel-loader






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 13 '18 at 5:22









      Arkadiy Stepanov

      68211




      68211
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Try running npm cache clean and reinstalling using npm install, then rebuilding.






          share|improve this answer





















          • Gives error npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one. npm ERR! npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
            – Arkadiy Stepanov
            Nov 13 '18 at 5:32












          • You might try npm cache clean --force, but proceed at your own risk. Although, I'm not sure of any major implications if you do.
            – Riley Steele Parsons
            Nov 13 '18 at 5:39











          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%2f53274318%2fbabel-7-0-and-webpack-fail%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          Try running npm cache clean and reinstalling using npm install, then rebuilding.






          share|improve this answer





















          • Gives error npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one. npm ERR! npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
            – Arkadiy Stepanov
            Nov 13 '18 at 5:32












          • You might try npm cache clean --force, but proceed at your own risk. Although, I'm not sure of any major implications if you do.
            – Riley Steele Parsons
            Nov 13 '18 at 5:39
















          0














          Try running npm cache clean and reinstalling using npm install, then rebuilding.






          share|improve this answer





















          • Gives error npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one. npm ERR! npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
            – Arkadiy Stepanov
            Nov 13 '18 at 5:32












          • You might try npm cache clean --force, but proceed at your own risk. Although, I'm not sure of any major implications if you do.
            – Riley Steele Parsons
            Nov 13 '18 at 5:39














          0












          0








          0






          Try running npm cache clean and reinstalling using npm install, then rebuilding.






          share|improve this answer












          Try running npm cache clean and reinstalling using npm install, then rebuilding.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 13 '18 at 5:27









          Riley Steele Parsons

          23116




          23116












          • Gives error npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one. npm ERR! npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
            – Arkadiy Stepanov
            Nov 13 '18 at 5:32












          • You might try npm cache clean --force, but proceed at your own risk. Although, I'm not sure of any major implications if you do.
            – Riley Steele Parsons
            Nov 13 '18 at 5:39


















          • Gives error npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one. npm ERR! npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
            – Arkadiy Stepanov
            Nov 13 '18 at 5:32












          • You might try npm cache clean --force, but proceed at your own risk. Although, I'm not sure of any major implications if you do.
            – Riley Steele Parsons
            Nov 13 '18 at 5:39
















          Gives error npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one. npm ERR! npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
          – Arkadiy Stepanov
          Nov 13 '18 at 5:32






          Gives error npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use `npm install --cache /tmp/empty-cache` to use a temporary cache instead of nuking the actual one. npm ERR! npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
          – Arkadiy Stepanov
          Nov 13 '18 at 5:32














          You might try npm cache clean --force, but proceed at your own risk. Although, I'm not sure of any major implications if you do.
          – Riley Steele Parsons
          Nov 13 '18 at 5:39




          You might try npm cache clean --force, but proceed at your own risk. Although, I'm not sure of any major implications if you do.
          – Riley Steele Parsons
          Nov 13 '18 at 5:39


















          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%2f53274318%2fbabel-7-0-and-webpack-fail%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

          Bressuire

          Vorschmack

          Quarantine