Open MichaelJCole opened 5 years ago
I just noticed this in the output:
[*] Running eslint --fix to comply with chosen preset rules...
So this may likely be an already solved problem.
thanks - I need to lint that too.
I think general issue with webpack and eslint - i struggle with this on both nuxt builds and quasar. Easy fix is in build config:
build: {
scopeHoisting: true,
// vueRouterMode: 'history',
// vueCompiler: true,
// gzip: true,
// analyze: true,
// extractCSS: false,
extendWebpack (cfg) {
cfg.module.rules.push({
enforce: 'pre',
test: /\.(js|vue)$/,
loader: 'eslint-loader',
exclude: /node_modules/, <- (comma)
-> options: {
-> fix: true
-> }
})
}
},
This might be a more general Quasar extension bug. While testing this extension I got the error below because the file created by
quasar ext add
didn't conform to the eslint settings fromquasar create
. This error breaks the "magic" of automated code scaffolding tools.Some options might be:
1) put
/* eslint-disable */
a the top of files at extension creation w/ notes in the extension docs. 2) reformat files after copying them (no idea how) 3) ?