Repository navigation
fix: install pusher-js so Echo can boot in production - #138
Merged
Merged
Conversation
added 2 commits
September 14, 2026 18:28
@laravel/echo-vue imports pusher-js for the Reverb transport. Without it the production Echo chunk throws and every signed-in page logs "Could not resolve pusher-js" in the console.
The install itself is the fix; a test that only reads package.json does not earn its keep.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@laravel/echo-vueimportspusher-jsbecause Reverb speaks the Pusher protocol. Lua never declared that peer, so the production Echo chunk threwCould not resolve "pusher-js"on every signed-in page.pusher-jsas a devDependency so Vite can bundle it.Test plan
pusher-jsresolve error.