All notable changes to this project will be documented in this file.
- Namespace regex patterns and documentation links (credit: PitPietro)
- Automatic server registration with .ts and .mjs extensions (credit: ohashi14715369)
- Dependency on vue-template-compiler (which should have never been there)
- Reverted changes introduced in 1.1.20
- Make NuxtSocketOpts and NuxtSocket non-partial (credit: CS_Birb)
- Type definitions file because socket.io-client types changed (credit: matthiasbaldi)
- Wired up support for the socket.io server options
- Socket.io dependencies to v4
- Support for using $nuxtSocket in the composition api.
- Middleware registration feature (sub namespaces)
- Feature to access the
ioinstance in the sub namespaces.
- Middleware registration feature (root namespace)
- Feature to access the
ioinstance in the root namespace.
- socket.io and socket.io-client deps to v3
- Ran security audit fix
- Option to disable the console.info messages (@ArticSeths)
- Types for plugin and module (@wkillerud)
- Ran security audit and updated dependencies.
- Badges to improve branding score on npms. (FaCuZ)
- Namespace path resolution on Windows for real this time. Merged in the change. (filipepinheiro)
- Namespace path resolution on Windows for real this time. Merged in the change.
- Support for .ts and .mjs namespace files
- Namespace path resolution on Windows.
- Support for Nuxt 2.13+ runtime config feature. Experimental feature.
- Changed internal workings of socket persistence. Socket instances are no longer being persisted in vuex, but instead internally by the plugin. This may break any code that relies on accessessing the sockets directly from vuex.
- Reverted to 1.1.2. Module is back in ESM. I think going forward, if CJS is needed, a duplicate or built file with .cjs will be created. It seems like the future is going towards ESM.
- module to CommonJS format. may be easier to re-use this way for now.
- consola to console in the module.
- consola to console in the plugin. Allows logging statements to be dropped with TerserWebpack plugin.
- Much cleaner documentation, hosted on their own site
- This github's README. I consider this to be a major change in docs, even though the code change was minor. Code was just linted.
- Automatic IO Server registration based on presence of IO server file and folder (added to module)
- Default handler for url missing. Now
window.locationwill be used.
- Before when URL was empty, an error would be thrown. Now it will just be a warning.
- Instance options for vuex and namespace config (that will override nuxt.config entries)
- Registration of $nuxtSocket vuex module
- Persistence of a given socket (using the "persist" option)
- Registration of serverAPI methods and events, with loose peer-detection
- Registration of clientAPI methods and events
- Default value of "teardown" option. Previous versions had it default to true. Now it defaults to the opposite of the "persist" value (persist defaults to false, therefore teardown to true, just like before)
- Pre-emit hook validation feature for emitbacks; if validation fails, emit event won't be sent.
- propExists method in the plugin. Properly checks to see if the property is defined.
- Pre-emit hook validation feature; if validation fails, emit event won't be sent.
- Before, emitter "args" would not be used if they were set to
false. A more proper check has replaced the old one.
- Improved documentation on usage
- Testing section in the docs; i.e., how to mock NuxtSocket, and how to inject.
- Added a safeguard against duplicate registration of Vuex listeners
- Added documentation on the auto-teardown feature
- Added option to disable console warnings in non-production mode.
- Took out the warning about the emitBack being an object.
- Added a fix for the case where an emitter response is undefined. I have a line the attempts to destructure resp to get
emitError, but it can't do that if resp is undefined. With the fix it can.
- Added debug logging feature
- Allow objects defined in Vuex state to be emitted back. Before I disallowed it (only allowed primitives), but I now enabled it because some developers may want that. I still warn the user about emitting the entire object when it may be desired to just emit the properties that have changed.
- Potential duplicate emitback registrations now prevented in non-test environment. Previous version only prevented it in the TEST env.
- Hosted demo, split across heroku (server) and netlify (client)
- Contributing guidelines.
- Improved documentation, and now host them on the
gh-pagesbranch. Docs now have a table of contents
- Minor bug fix in the chat rooms example (
@keyup.enterdefined on the input message just needed to be updated)
Important NOTE: The maintainer of this project will be away from keyboard for this time. If issues arise in 1.0.11, please consider reverting to v1.0.10 or deferring your issues until I return. Thanks for your understanding!
- Moved plugin utils back into plugin. It seemed like the utils were not getting built by Nuxt.
- Error-handling feature for emitters. Handles both timeout and non-timeout kinds of errors.
- Feature to pass arguments to the emitter function (arguments would take priority over the "msg" specified in emitters config in
nuxt.config)
- Fixed potential overwriting of emitter methods by properly setting
mapTo. (overwriting could have accidentally been done by the call toassignResp) - Expanded test timeout to fix broken tests
- Minor change: v1.0.9 accidentally packaged
plugin.compiled.jswhich is only used for tests and not needed in the distro.
- SocketStatus feature. Disabled by default, opt-in to use it. SocketStatus component will also be included now.
- Potential stack overflow error in the auto-teardown code; error was only noticeable when multiple nuxtSockets were instantiated on the same component. The error was fixed.
- Fixed
propByPathmethod, which was incorrectly treating empty (falsy) strings as undefined.
- Support for namespace configuration
- Chat rooms example in
examples/roomsbranch. - Automated tests for new feature and example pages.
- Internally, refactored some of the plugin code to improve readability, input validation and consistency.
- Organization of automated tests. Tests now run a bit faster and are easier to maintain.
- Check to see if specified emitbacks exist in Vuex store. If they don't, provide friendly error message
- Moved examples to components. Added tests. Eliminated need for the old and slow e2e tests
- Updated plugin tests.
- Potential duplicate emitback registrations now prevented
- [Dev server] ioServer.listen resolves correctly now
- Check for missing vuex options; i.e., missing mutations or actions
- Only export plugin opts in TEST mode
- TEST mode can get/set plugin opts from outside the plugin, non-TEST mode can only get plugin opts inside the plugin
- Improved Test coverage. Now at 100%
- Badges format
- Unit tests to help get better test coverage
- This changelog