Open justb4 opened 2 years ago
Wanted to get rid of using npm install --legacy-peer-dep
. Finally completely re-scaffolded the project using global install of node v16.13.0
, npm 8.1.0
and @vue/cli 4.5.15
:
vue create
with custom options, selecting vuex
and router
vuetify
npm install
devDependencies
eslinting
errors due to version conflictshttps://github.com/justb4/M-Dash/commit/b4d1ec82d784a5c50ead8c3867048e2c48488b6d now has working version though some eslinting has been disabled. But a clean build without JS console errors (except for those mentioned earlier), using:
rm -rf node_modules package-lock.json
npm cache clean --force
npm install
npm run serve
Cool thanks man! I'll give it a look over when I have some free time but this is appreciated
Thanks @ClintOxx for this awesome project! Hopefully we can all help here to maintain.
Getting various build and run errors due to outdated and deprecated package versions. Resolved locally, will submit PR. Context:
master
as on nov 29, 2021node
v16.13.0,npm
8.1.0,@vue/cli
4.5.15, installed with Homebrew andnvm
First try with plain
npm install
Next tried install with
npm install --legacy-peer-deps
to suppress dependency errors. Output:Main error is
gyp
build. Even if I configure to usepython 2.7
withpyenv
, I keep gettinggyp
errors. Problem is that the librarynode-sass
requires Python2 to build, but Python2 is also EOL. Replacing with"sass": "1.43.5"
think, written in Dart, gets rid of this problem. Now could runnpm install --legacy-peer-deps
OK.Trying to run:
npm run dev --open
goteslint
errors, though non-fatal.Solution: replace
"babel-eslint": "^10.1.0"
with"@babel/eslint-parser": "^7.16.3"
.Now almost there: "multiword" rule Vue Style issues:
Can be suppressed by listing single word exceptions in
eslintrc.js
See https://eslint.vuejs.org/rules/multi-word-component-names.html.Also upgraded many versions in
package.json
, final build result, still withnpm install --legacy-peer-deps
:No warnings on run, app runs in browser ok, at least with two runtime errors. These also found in official demo, so may need separate issues/PRs:
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
, but could be due to my browser (Brave).As said will PR shortly.