You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// or return object to be merged with webpack-merge
67
67
})
68
68
69
-
api.regsiterCommand('test', args=> {
69
+
api.registerCommand('test', args=> {
70
70
// register `vue-cli-service test`
71
71
})
72
72
}
@@ -80,7 +80,7 @@ An important thing to note about env variables is knowing when they are resolved
80
80
module.exports=api=> {
81
81
process.env.NODE_ENV// may not be resolved yet
82
82
83
-
api.regsiterCommand('build', () => {
83
+
api.registerCommand('build', () => {
84
84
api.setMode('production')
85
85
})
86
86
}
@@ -103,7 +103,7 @@ module.exports = api => {
103
103
A plugin can retrieve the resolved webpack config by calling `api.resolveWebpackConfig()`. Every call generates a fresh webpack config which can be further mutated as needed:
Alternatively, a plugin can also obtain a fresh [chainable config](https://github.com/mozilla-neutrino/webpack-chain) by calling `api.resolveChainableWebpackConfig()`:
0 commit comments