-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
dependancy and ERROR thrown during installation and vue serve #2860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Quick fix: Changed Home.vue: But there must be a better way. |
this is still happening in last version, please reopen |
@cristiangiagante Please provide more information and also check if it's the same issue as #3243 |
I'm having the same problem |
If using |
I am having the same problem but only within a multi-stage docker build and only when ran from a gitlab-runner. I have components under src/components/layout/{component} and I am importing them with Dockerfile # build stage
FROM node:12-alpine as build-stage
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
RUN npm run build
# production stage
FROM nginx:stable-alpine as production-stage
COPY --from=build-stage /app/dist /usr/share/nginx/html
EXPOSE 80
CMD ["nginx", "-g", "daemon off;"] babel.config.js module.exports = {
presets: [
'@vue/cli-plugin-babel/preset',
],
plugins: [
'@babel/plugin-syntax-dynamic-import',
],
}; vue.config.js module.exports = {
css: {
loaderOptions: {
scss: {
prependData: '@import "~@/styles/variables.scss";',
},
},
},
}; .eslintrc.js module.exports = {
root: true,
env: {
node: true,
browser: true,
es2020: true,
},
extends: [
// add more generic rulesets here, such as:
// 'eslint:recommended',
'plugin:vue/essential',
'@vue/airbnb',
],
parserOptions: {
parser: 'babel-eslint',
},
rules: {
// override/add rules settings here, such as:
// 'vue/no-unused-vars': 'error'
'import/extensions': ['error', 'always', {
js: 'never',
vue: 'never',
}],
},
settings: {
'import/resolver': {
alias: {
map: [
['@', './src'],
],
extensions: ['.js', '.vue'],
},
},
},
overrides: [
{
files: [
'**/__tests__/*.{j,t}s?(x)',
'**/tests/unit/**/*.spec.{j,t}s?(x)',
],
env: {
mocha: true,
},
},
],
}; |
@Matthew-Benson facing exactly the same problem like you! Local build (on windows machine) runs perfect. Build on GitLab CI Runner (inside kubernetes) fails, because of missing dependency. Changing from '@/components/...' to '../components/....' doesn't solve the problem. Versions: Any hints or version downgrades which might solve this? |
@stefanhettich I'm so sorry! I did the classic bad-developer thing of solving my problem and not coming back to update what my solution was. My issue was that I am using a case-insensitive file-system on MacOS - I named the folder in question I opened the repo in the gitlab editor and renamed the folder there to Changing the folder casing on my Mac never got committed and pushed up because the file system sees no difference. Hope that helps! |
@Matthew-Benson Thank you so much for your response! It was exactly the same thing in my case. I had several mixins like Nevertheless, the issue is fixed, you saved my day! Thanks a lot! |
Version
3.0.5
Reproduction link
https://github.com/ctfrancia/shop
Node and OS info
npm 5.6.0
Steps to reproduce
vue serve
What is expected?
to show the application after running the command
What is actually happening?
This dependency was not found:
To install it, you can run: npm install --save @/components/HelloWorld.vue
I have uninstalled and reinstalled both vue and @vue/cli. updated npm and reinstalled. During installation errors are thrown:
ERROR Error: No files matching 'tests' were found.
Error: No files matching 'tests' were found.
-------- ALSO --------
[email protected] requires a peer of graphql@^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN @apollographql/[email protected] requires a peer of graphql@^0.13.1 but none is installed. You must install peer dependencies yourself.
This is a new bug and has never happened previously while starting a new project/running an old project.
The text was updated successfully, but these errors were encountered: