[BUG] npm v6.14.xx : 'npm install' generate different node_modules which made my project not responding
gesangseto opened this issue · comments
At first I wanted to archive my stable project (archive_project) because it would be upgraded to the next version, what I did was copy all the files folder except node_modules to the folder (next_project).
then I ran npm install
(next_project) everything went smoothly.
When I run dev npm run serve
and try the project (next_project) it takes too long to load and often doesn't respond on browser, even if the display can load correctly, expanding the menu or clicking a button doesn't seem to respond.
I think this happens because the node_modules are generated by npm install
because if the latest project (next_project) uses node_modules from the project that I archived (archive_project) there are no problems whatsoever
The image below is the date node_modules (archive project) was modified, so I rolled back package.json (next_project) before that date but to no avail
I have changed several versions of nodejs:
v12.22.12, v14.20.0, v16.20.0
depedency
{
"name": "My Project",
"version": "3.0.0",
"description": "-",
"author": {
"name": "CoreUI",
"url": "https://coreui.io",
"github": "https://github.com/coreui",
"twitter": "https://twitter.com/core_ui"
},
"contributors": [
{
"name": "CoreUI Team",
"url": "https://github.com/orgs/coreui/people"
}
],
"scripts": {
"serve": "vue-cli-service serve",
"build": "vue-cli-service build",
"lint": "vue-cli-service lint",
"test:unit": "vue-cli-service test:unit",
"test:e2e": "vue-cli-service test:e2e",
"clearCache": "jest --clearCache",
"release": "npm-run-all clearCache lint build test:unit test:e2e"
},
"dependencies": {
"@adamdehaven/vue-custom-tooltip": "^1.4.4",
"@coreui/coreui": "^3.0.0",
"@coreui/icons": "^1.0.1",
"@coreui/icons-vue": "^1.3.5",
"@coreui/utils": "^1.2.4",
"@coreui/vue": "^3.0.6",
"@coreui/vue-chartjs": "^1.0.5",
"@fortawesome/fontawesome-free": "^6.0.0",
"apollo-link-http-common": "^0.2.16",
"axios": "^0.21.1",
"bwip-js": "^3.0.4",
"chart.js": "^2.9.4",
"crypto-js": "^4.1.1",
"dom-to-image": "^2.6.0",
"dotenv": "^8.2.0",
"expose-loader": "^1.0.0",
"jquery": "^3.5.1",
"jspdf": "^2.4.0",
"jsprintmanager": "^5.0.1",
"jstorage": "^0.4.8",
"jszpl": "^1.1.7",
"moment": "^2.28.0",
"readline": "^1.3.0",
"regenerator-runtime": "^0.13.11",
"simplestorage.js": "^0.2.1",
"vue": "~2.6.11",
"vue-awesome": "^4.3.1",
"vue-chartjs": "^3.5.1",
"vue-cli-plugin-compression": "^1.2.0",
"vue-cute-timeline": "^1.2.10",
"vue-excel-xlsx": "^1.0.11",
"vue-float-action-button": "^0.7.9",
"vue-html-to-paper": "^1.3.1",
"vue-js-modal": "^2.0.1",
"vue-material-design-icons": "^5.0.0",
"vue-multilanguage": "^4.0.10",
"vue-print-nb": "^1.5.0",
"vue-router": "~3.1.6",
"vue-search-select": "^2.9.2-alpha.3",
"vue-select": "^3.10.8",
"vue-toast-notification": "^0.4.1",
"vue-touch-keyboard": "^0.3.2",
"vue2-datepicker": "^3.8.2",
"vue2-daterange-picker": "^0.6.7",
"vuejs-datepicker": "^1.6.2",
"vuejs-loading-screen": "^1.0.9",
"vuelidate": "^0.7.5",
"vuelidate-error-extractor": "^2.4.1",
"vuex": "~3.1.3"
},
"devDependencies": {
"@babel/core": "~7.9.0",
"@vue/cli-plugin-babel": "~4.3.1",
"@vue/cli-plugin-e2e-nightwatch": "~4.3.1",
"@vue/cli-plugin-eslint": "~4.3.1",
"@vue/cli-plugin-unit-jest": "~4.3.1",
"@vue/cli-service": "~4.3.1",
"@vue/test-utils": "1.0.0-beta.29",
"babel-core": "^6.26.3",
"babel-eslint": "~10.1.0",
"babel-jest": "~25.2.6",
"babel-loader": "^8.2.2",
"babel-polyfill": "^6.26.0",
"babel-preset-es2015": "^6.24.1",
"babel-preset-stage-0": "^6.24.1",
"core-js": "^3.27.1",
"eslint": "~6.8.0",
"eslint-plugin-vue": "~6.2.2",
"node-sass": "^4.14.1",
"npm-run-all": "~4.1.5",
"sass-loader": "~8.0.2",
"vue-template-compiler": "~2.6.11"
},
"browserslist": [
"> 1%",
"last 2 versions",
"not ie <= 9"
],
"engines": {
"node": ">= 8.10.x",
"npm": ">= 5.6.0"
}
}
```
This does not seem to be a bug with npm but more of a support question for the software you're trying to run. You may want to try more general support forums, or ask in places where vue
offers support (this appears to be a vue
app based on the dependencies, or if you think this really is something npm related you may try opening a discussion at https://github.com/orgs/community/discussions.
Additionally, please use the full issue template when opening issues. npm version 6 has not been supported in many years.