-
Notifications
You must be signed in to change notification settings - Fork 48
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.
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
Version 3.0.0 #170
Version 3.0.0 #170
Conversation
* Removed deprecated parameters * Updates dependencies * Reload now returns a promise * Functions in the return API also return promises * Reload returns errors in promises * Added unit tests. * Added coverage analyzer * Coverage 100% on `reload.js` file * `startWebSocketServer` is the return API is not defined if the WebSocket wait option is not used
In the readme, it states to push a script tag down to the client as follows: <script src="/reload/reload.js"></script> That said, it isn't too clear that "/reload/reload.js" is a route that reload sets up in the express app. |
…ates * Added support for P12/PFX HTTPS files * Added forceWss option which forces the client to connect over `wss` even when the window is `https`
Hi! Any progress with this? Do you have any planned date for releasing 3.0.0? |
@meszaros-lajos-gyorgy sorry this is taking so long, I just have to make a couple of tweaks and then get it out. I'll see if I can get it out in the next two weeks |
Thank you! |
…ted this new logic with unit tests.
Added two new tests to test that the `startWebSocketServer` function is only returned when the option is enabled
@meszaros-lajos-gyorgy in case you missed this. This is now merged and published to npm. |
Version 3.0.0
Consult Migration Guide for help with updating from Version 2.x to 3.x
Breaking/Removed
Breaking/Added
closerServer
startWebSocketServer
Added
reload.js
filenpm ci install
for CI #158)Changed
Closes the following issues:
npm ci install
for CI #158 (Closes Investigate/implementnpm ci install
for CI #158)