davellanedam / vue-skeleton-mvp Goto Github PK

As soon as any file is modified, the ESlint kicks in with heaps of problems (practically all files), and these errors can't be ignored as they are forwarded to the client on a glass pane.

Example. Adding a single empty line in About.vue and I get this, relatively small, list of issues;

 ERROR  Failed to compile with 1 error                                                                                                                                                                      12:37:42 PM

 error  in ./src/components/About.vue

Module Error (from ./node_modules/eslint-loader/index.js):

/home/niclas/dev/pony/think4web/src/components/About.vue
  5:1  warning  Trailing spaces not allowed  no-trailing-spaces
  5:1  error    Delete `······`              prettier/prettier

✖ 2 problems (1 error, 1 warning)
  1 error and 1 warning potentially fixable with the `--fix` option.


 @ ./src/router/routes/about.js 81:11-83:29
 @ ./src/router/routes sync nonrecursive \.js$
 @ ./src/router/routes/index.js
 @ ./src/router/index.js
 @ ./src/main.js
 @ multi (webpack)-dev-server/client?http://192.168.1.42:8080&sockPath=/sockjs-node (webpack)/hot/dev-server.js ./src/main.js

Hi, first off, I've got to say that this project is amazing! However I have a question, I was trying to implement in my project the part of loading, error, success. But I get this errors:

[vuex] unknown local mutation type: SHOW_LOADING, global type: users/SHOW_LOADING
[vuex] unknown local mutation type: SUCCESS, global type: users/SUCCESS
[vuex] unknown local mutation type: ERROR, global type: users/ERROR
[vuex] unknown local mutation type: SUCCESS, global type: users/SUCCESS

I think it's because of something with namespacing (because my module has it, while loading, error, and success don't) What can it be the approach to solve this? I read that I have to use something with '{root:true}", I tried to put it in every commit in the part of utils.js, and now I don't get the error, but it still doesn't show me the components, what do you think this could be?

Downloaded the repo, extract, cd into the project, and i ran

npm install

struck with this error

gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.

Is your feature request related to a problem? Please describe.
There currently is no problem

Describe the solution you'd like
Vue has updated to major version 3. This will bring performance improvements and keep the project fresh.

Describe alternatives you've considered
We could remain at version 2, but that may not work long term

Additional context
Here's the release news for version 3 of vue:
https://news.vuejs.org/issues/186
Here's a basic guide for update from version 2 to 3:
https://dev.to/blacksonic/the-vue-3-upgrade-guide-4dc4

Describe the bug
Thanks for an amazing boilerplate. I keep experiencing a failed start though. Whenever I try to start using yarn serve, I get the error

To Reproduce
Steps to reproduce the behavior:
I decided to use yarn instead of npm.

• Clone the repo
• Run yarn to install packages.
• Run yarn serve to start the project

Expected behavior
vue-cli should successfully serve the app locally. The simple fix has been to install @vue/babel-preset-app using the command
yarn add -D @vue/babel-preset-app

Is anyone else experiencing the same issue? I can create a PR to resolve it but I find it strange that no one might have experienced this.

Screenshots

Describe the bug

Which version of npm is required for this project? I don't see it documented in the README.md

To Reproduce

Using npm version 8.1.0

npm update returns following error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree

npm run serve returns the following error:

40% building 118/149 modules 31 active /node_modules/vee-validate/dist/vee-validate.esm.jsAssertion failed: (thread_id_key != 0x7777), function find_thread_id_key, file coroutine.cc, line 134.

http://localhost:3000 fails to load

Expected behavior

I expected the project to properly bootstrap

Screenshots
If applicable, add screenshots to help explain your problem.

OS: MacOS
Version Sonoma v14.3.1

Hi Daniel,
thanks for sharing your excellent mvp.

I'm having this error: "sockjs.js?9be2:1606 GET https://localhost/sockjs-node/info?t=1579773805212 net::ERR_CONNECTION_REFUSED"
what should I modify in order to solve it?

I added the local address in vue.config.js, but still got the problem:

module.exports = {
  productionSourceMap: false,
  pluginOptions: {
    i18n: {
      enableInSFC: true
    }
  },
  devServer: {
   host: '192.168.1.7'
  }
}

Marco

Describe the bug
Documentation says

npm install
npm update

but npm update fails on my system with the following error message (which I think says that @vue/[email protected] depends on an earlier eslint).

niclas@d1:~/dev/pony/think4web$ npm update
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^7.18.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">= 1.6.0 < 7.0.0" from @vue/[email protected]
npm ERR! node_modules/@vue/cli-plugin-eslint
npm ERR!   dev @vue/cli-plugin-eslint@"^4.5.11" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/niclas/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/niclas/.npm/_logs/2021-02-17T11_30_55_926Z-debug.log

Describe the bug
HelloWorld.vue is referred to in tests but it does not exist. This causes tests to fail

To Reproduce
Run npm test:unit or yarn test:unit

Expected behavior
The test should pass

Screenshots
If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

• OS: macOS
• Version Catalina

As i mention i title, Why not using vuetify 2?

Taken today off of latest: