Building the frontend with gulp - is it possible to optimize the environment!?

Question

Building projects

Fully automated front end build with Gulp.
Optimization question. For example, there are 20 identical projects (layout) and in each one, after expanding all Gulp's dependencies (see devDependencies), an overfigure of subfolders (600+) is created in the project environment in the node_modules dependencies folder. An isolated environment for each project is, of course, good and right ... But is it possible to somehow globally pull all these dependencies (because they are absolutely identical) from project to project ... It's a pity SSD-hu. Or is it impossible!? Answers like: use another assembler - not relevant... I would be grateful for any advice.

"devDependencies": {
    "bootstrap-sass": "^3.3.7",
    "browser-sync": "^2.14.0",
    "gulp": "^3.9.1",
    "gulp-autoprefixer": "^3.1.0",
    "gulp-clean-css": "^2.0.12",
    "gulp-if": "^2.0.1",
    "gulp-imagemin": "^3.0.2",
    "gulp-plumber": "^1.1.0",
    "gulp-rigger": "^0.5.8",
    "gulp-ruby-sass": "^2.0.6",
    "gulp-sourcemaps": "^1.6.0",
    "gulp-svgmin": "^1.2.2",
    "gulp-uglifyjs": "^0.6.2",
    "gulp-wait": "0.0.2",
    "imagemin-gifsicle": "^5.1.0",
    "imagemin-jpeg-recompress": "^5.1.0",
    "imagemin-jpegtran": "^5.0.2",
    "imagemin-optipng": "^5.2.0",
    "imagemin-pngquant": "^5.0.0",
    "imagemin-svgo": "^5.2.0",
    "rimraf": "^2.5.4"
  },

upd; as they say "good idea ..."! After the question was asked, it occurred to me to try SymLinks (as an option)

Answer 1

https://docs.npmjs.com/cli/link _

npm link gulp
npm link gulp-less
npm link gulp-watch
npm link gulp-autoprefixer
npm link gulp-plumber
npm link path