Vetur: flatmap-stream is referenced in Vetur's yarn.lock

Created on 27 Nov 2018  路  2Comments  路  Source: vuejs/vetur

  • [x] I have searched through existing issues
  • [x] I have read through docs
  • [x] I have read FAQ

Info

  • Platform: Linux
  • Vetur version: 0.14.2
  • VS Code version: 1.29.1

Problem

As described here: https://github.com/dominictarr/event-stream/issues/116

./.vscode/extensions/octref.vetur-0.14.1/yarn.lock:712:    flatmap-stream "^0.1.0"
./.vscode/extensions/octref.vetur-0.14.1/yarn.lock:891:flatmap-stream@^0.1.0:
./.vscode/extensions/octref.vetur-0.14.1/yarn.lock:893:  resolved "https://registry.yarnpkg.com/flatmap-stream/-/flatmap-stream-0.1.1.tgz#d34f39ef3b9aa5a2fc225016bd3adf28ac5ae6ea"
./.vscode/extensions/octref.vetur-0.14.2/yarn.lock:712:    flatmap-stream "^0.1.0"
./.vscode/extensions/octref.vetur-0.14.2/yarn.lock:891:flatmap-stream@^0.1.0:
./.vscode/extensions/octref.vetur-0.14.2/yarn.lock:893:  resolved "https://registry.yarnpkg.com/flatmap-stream/-/flatmap-stream-0.1.1.tgz#d34f39ef3b9aa5a2fc225016bd3adf28ac5ae6ea"


Reproducible Case

Just install Vetur.

bug

Most helpful comment

I also want to make it clear these come from the dev dependencies, and those are removed for bundling & publishing. In conclusion: you might see references to flatmap-stream in your local installs of Vetur, but not the actual node module of flatmap-stream. You are safe 馃槃

However, if you have been developing / contributing to Vetur, you might be affected. Please take time to do these:

yarn cache clean gulp-untar
yarn cache clean npm-run-all

And reinstall dependencies in the repo.

All 2 comments

Fixed and will publish soon. Thanks for the heads-up.

I also want to make it clear these come from the dev dependencies, and those are removed for bundling & publishing. In conclusion: you might see references to flatmap-stream in your local installs of Vetur, but not the actual node module of flatmap-stream. You are safe 馃槃

However, if you have been developing / contributing to Vetur, you might be affected. Please take time to do these:

yarn cache clean gulp-untar
yarn cache clean npm-run-all

And reinstall dependencies in the repo.

Was this page helpful?
0 / 5 - 0 ratings