Skip to content

Conversation

@snyk-bot
Copy link

Snyk has created this PR to upgrade meteor-node-stubs from 0.3.2 to 0.4.1.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 3 versions ahead of your current version.
  • The recommended version was released 3 years ago, on 2018-05-08.
Release notes
Package name: meteor-node-stubs
  • 0.4.1 - 2018-05-08

    Bump npm version to 0.4.1 in preparation for publishing.

  • 0.4.0 - 2018-05-08

    Bump npm version to 0.4.0 in preparation for publishing.

  • 0.3.3 - 2018-03-06

    Bump NPM version to 0.3.3 in preparation for publishing.

  • 0.3.2 - 2017-10-19

    Bump NPM version to 0.3.2 in preparation for publishing.

from meteor-node-stubs GitHub release notes
Commit messages
Package name: meteor-node-stubs
  • 998d5a7 Bump npm version to 0.4.1 in preparation for publishing.
  • d88681f Correctly obtain named Buffer export from "buffer" built-in.
  • 5e403de Bump npm version to 0.4.0 in preparation for publishing.
  • f64e023 Update npm-shrinkwrap.json to package-lock.json.
  • d52c306 Install [email protected] from npm rather than our fork.
  • fc83c29 Define Buffer globally if buffer built-in module installed.
  • 6c3e31a Bump NPM version to 0.3.3 in preparation for publishing.
  • 5ab4c51 Update npm-shrinkwrap.json.
  • 81710aa Bump string_decoder to latest version.
  • 4880599 Replace unmaintained http-browserify with stream-http (#13)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants