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

Failed to load resource: the server responded with a status of 404 () #845

Closed
jennifer671 opened this issue May 14, 2021 · 5 comments
Closed

Failed to load resource: the server responded with a status of 404 () #845

jennifer671 opened this issue May 14, 2021 · 5 comments
Labels
bug confirmed acknowledged as an issue released on @rc released
Milestone
2.0.0

Comments

@jennifer671
Copy link

jennifer671 commented May 14, 2021 •
edited
Loading

I'm using peerjs in my webRTC videoChat. when I start the demo this is the error. I have the same error on Chrome and Safari too. How can I fix this problem ?
looking forward to someone reply.
Schermata 2021-05-14 alle 16 38 37
Schermata 2021-05-14 alle 16 37 53
@oualid-cher
Copy link

same problem and all what i found till know is how to hide the message(go to inspect->console->settings->selected context only(enbale the box)). hope to get the solution though

@afrokick
Copy link
Member

Could you please check the beta version? It should has a fix for it.

npm i peerjs@beta

@afrokick afrokick added this to the 2.0.0 milestone Feb 20, 2022
@afrokick afrokick added bug confirmed acknowledged as an issue labels Feb 20, 2022
@carliey
Copy link

carliey commented Apr 26, 2022

have you found a solution?

jonasgloning added a commit that referenced this issue Apr 27, 2022
@jonasgloning
feat: upgrade to Parcel@2
a2e942e 
- smaller bundle 
- better source maps
- improved bundler compatibility

Closes #845, #859, #552, #585
@github-actions
Copy link

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

The release is available on:

Your semantic-release bot 📦🚀

github-actions bot pushed a commit that referenced this issue May 10, 2022
@semantic-release-bot @jonasgloning
chore(release): 1.4.0 [skip ci]
8bd83df 
# [1.4.0](v1.3.2...v1.4.0) (2022-05-10)

### Bug Fixes

* add changelog and npm version to the repo ([d5bd955](d5bd955))
* add token to PeerJSOption type definition ([e7675e1](e7675e1))
* websocket connection string ([82b8c71](82b8c71))

### Features

* upgrade to Parcel@2 ([aae9d1f](aae9d1f)), closes [#845](#845) [#859](#859) [#552](#552) [#585](#585)

### Performance Improvements

* **turn:** lower TURN-latency due to more local servers ([a412ea4](a412ea4))
@github-actions
Copy link

🎉 This issue has been resolved in version 1.4.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug confirmed acknowledged as an issue released on @rc released
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
4 participants
@afrokick @carliey @oualid-cher @jennifer671