Skip to content
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.

Sign up for GitHub

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

Jump to bottom

npm WARN deprecated [email protected] #287

Closed
Valexr opened this issue Sep 30, 2022 · 2 comments
Closed

npm WARN deprecated [email protected] #287

Valexr opened this issue Sep 30, 2022 · 2 comments
Labels
released on @rc

Comments

@Valexr
Copy link

Valexr commented Sep 30, 2022

I'm having an issue:

  • Give an expressive description of what is went wrong
  • Version of peer you're experiencing this issue
  • Nodejs version?
  • Platform name and its version (Win, Mac, Linux)?
  • Nice to have: a repository with code to reproduce the issue
  • If you're getting an error or exception, please provide its full stack-trace as plain-text or screenshot

I have a suggestion:

  • Describe your feature / request
  • How you're going to use it? Give a usage example(s)

Documentation is missing something or incorrect (have typos, etc.):

  • Give an expressive description what you have changed/added and why
  • Make sure you're using correct markdown markup
  • Make sure all code blocks starts with triple ``` (backtick) and have a syntax tag, for more read this docs
  • Post addition/changes in issue, we will manage it

Thank you, and do not forget to get rid of this default message
github-actions bot pushed a commit that referenced this issue Oct 29, 2022
@semantic-release-bot @jonasgloning
chore(release): 1.0.0-rc.1 [skip ci]
d425f49 
# [1.0.0-rc.1](v0.6.1...v1.0.0-rc.1) (2022-10-29)

### Bug Fixes

* **npm audit:** Updates all dependencies that cause `npm audit` to issue a warning ([1aaafbc](1aaafbc)), closes [#287](#287)

### Features

* drop Node {10,11,12,13} support ([b70ed79](b70ed79))

### Performance Improvements

* use the builtin UUID generator for Peer ids instead of the `uuid` module ([5d882dd](5d882dd))

### BREAKING CHANGES

* Node >= 14 required

14 is the oldest currently supported version. See https://github.com/nodejs/release#release-schedule
@github-actions
Copy link

🎉 This issue has been resolved in version 1.0.0-rc.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

github-actions bot pushed a commit that referenced this issue Oct 30, 2022
@semantic-release-bot @jonasgloning
chore(release): 1.0.0-rc.1 [skip ci]
3ca59a1 
# [1.0.0-rc.1](v0.6.1...v1.0.0-rc.1) (2022-10-30)

### Bug Fixes

* **npm audit:** Updates all dependencies that cause `npm audit` to issue a warning ([1aaafbc](1aaafbc)), closes [#287](#287)

### Features

* drop Node {10,11,12,13} support ([b70ed79](b70ed79))
* remove deprecated XHR fallback ([d900145](d900145))

### Performance Improvements

* use the builtin UUID generator for Peer ids instead of the `uuid` module ([5d882dd](5d882dd))

### BREAKING CHANGES

* Requires PeerJS >= 1.0
* Node >= 14 required

14 is the oldest currently supported version. See https://github.com/nodejs/release#release-schedule
@peerjs-bot
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@peers peers locked as resolved and limited conversation to collaborators Feb 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
released on @rc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Valexr @peerjs-bot