Entrar Ainda não tem acesso?
Solucionado (ver solução)
Solucionado
(ver solução)
4
respostas

npm run build-dev error

Referente ao curso Webpack: Manipulando módulos na sua webapp

por Sérgio Schwartz Varejão
| 50.3k xp | 3 posts

client@1.0.0 build-dev C:\Users\sergi\OneDrive\Área de Trabalho\webPack alura\01-projeto-webpack\projeto-webpack\clientwebpack --config webpack.config.js

Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.

  • configuration has an unknown property 'modules'. These properties are valid: object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? } For typos: please correct them. For loader options: webpack 2 no longer allows custom properties in configuration. Loaders should be updated to allow passing options via loader options in module.rules. Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader: plugins: [
    new webpack.LoaderOptionsPlugin({
  // test: /\.xxx$/, // may apply this only for some modules
  options: {
    modules: ...
  }
})
    ] npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! client@1.0.0 build-dev: webpack --config webpack.config.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the client@1.0.0 build-dev script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\sergi\AppData\Roaming\npm-cache_logs\2020-08-12T18_38_14_911Z-debug.log PS C:\Users\sergi\OneDrive\Área de Trabalho\webPack alura\01-projeto-webpack\projeto-webpack\client>

4 respostas
por Laís Cavalcanti
| 2577.8k xp | 4815 posts
Instrutor

Oi, Sérgio, tudo bem?

Em que aula do curso você está? Se puder compartilhar aqui o seu webpack.config.js e o package.js para que possa testar e entender melhor o que aconteceu para esse erro.

por Sérgio Schwartz Varejão
| 50.3k xp | 3 posts

havia enviado o codigo errado. estou na aula 11, codigo na resposta a seguir

por Sérgio Schwartz Varejão
| 50.3k xp | 3 posts

webpack.config.js

const path = require('path');

module.exports = {
    entry: './app-src/app.js',
    output: {
        filename: 'bundle.js',
        path: path.resolve(__dirname, 'dist')
    },
    modules: {
        rules: [
            {
                test: /\.js$/,
                exclude: /node_modules/,
                use : {
                    loader: 'babel-loader'
                }
            }
        ]
    }

}

package.json

{
  "name": "client",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "build-dev": "webpack --config webpack.config.js"   
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "reflect-metadata": "^0.1.10"
  },
  "devDependencies": {
    "babel-core": "^6.25.0",
    "babel-loader": "^7.1.0",
    "babel-plugin-transform-decorators-legacy": "^1.3.4",
    "babel-preset-es2017": "^6.24.1",
    "webpack": "^3.1.0"
  }
}
solução!
por Cleyton
| 135.5k xp | 50 posts

Boa tarde.

Passei pelo mesmo problema e constatei que em: 

 modules: {
        rules: [
            {
                test: /\.js$/,
                exclude: /node_modules/,
                use : {
                    loader: 'babel-loader'
                }
            }
        ]
    }

modules na realidade e "module", no singular pelo menos resolveu meu problema e passou normal.

Boa sorte !