We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
esm-hmr
Apart from the HMR API, the WebSocket esm-hmr protocol should also be clearly specified.
As an example, GraphQL over WebSocket protocol specification is helpful.
According to this, and based on the current implementation, it is as follows:
hotAccept
Direction: Client -> Server
interface HotAcceptMessage { type: "hotAccept"; id: string; }
reload
Direction: Server -> Client
interface ReloadMessage { type: "reload"; }
update
interface UpdateMessage { type: "update"; url: string; }
You may want to unify the id and url fields.
id
url
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Apart from the HMR API, the WebSocket
esm-hmr
protocol should also be clearly specified.As an example, GraphQL over WebSocket protocol specification is helpful.
According to this, and based on the current implementation, it is as follows:
Message Types
hotAccept
Direction: Client -> Server
reload
Direction: Server -> Client
update
Direction: Server -> Client
You may want to unify the
id
andurl
fields.The text was updated successfully, but these errors were encountered: