rx-postmessenger | Minimal RxJS adapter for the window.postMessage API | HTTP Client library

by JJWesterkamp TypeScript Version: 3.0.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | rx-postmessenger Summary

rx-postmessenger is a TypeScript library typically used in Utilities, HTTP Client applications. rx-postmessenger has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Minimal RxJS adapter for the window.postMessage API for request-response streams and notification streams across frame windows.

Support

Quality

Security

License

Reuse

Support

rx-postmessenger has a low active ecosystem.

It has 18 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 3 have been closed. On average issues are closed in 17 days. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of rx-postmessenger is 3.0.0

Quality

rx-postmessenger has 0 bugs and 0 code smells.

Security

rx-postmessenger has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

rx-postmessenger code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

rx-postmessenger is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

rx-postmessenger releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

It has 3615 lines of code, 0 functions and 29 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of rx-postmessenger

Get all kandi verified functions for this library.

rx-postmessenger Key Features

No Key Features are available at this moment for rx-postmessenger.

rx-postmessenger Examples and Code Snippets

No Code Snippets are available at this moment for rx-postmessenger.

Community Discussions

Trending Discussions on rx-postmessenger

Does updating a package dependency by a major version require a major version bump of the package itself?

QUESTION

Does updating a package dependency by a major version require a major version bump of the package itself?

Asked 2018-Oct-30 at 02:36

I'm currently investigating the possibilities for upgrading an RxJS dependency from v5.5 to v6 in this package of mine. This is a relatively small npm package and after reading the migration guide I don't anticipate any problems implementing the new version.

The thing is I'm curious whether or not the new version of my package itself should be a new major version. I have always taken for granted the statement that as long as a piece of software retains the same public interface, changes to the implementation can be published with a minor or patch version bump.

Although my package interface should be able to remain unchanged, in this case I'm dealing with RxJS being a dependency that is also certainly used by anyone that uses my package. And because of the incompatibilities between the RxJS versions I'm switching between I would suspect a major version bump to be more appropriate. How do I reason about this topic?

...

ANSWER

Answered 2018-Oct-30 at 02:36

And because of the incompatibilities between the RxJS versions I'm switching between I would suspect a major version bump to be more appropriate

This is mostly legit and would be better to bump as major. You can consider 2 cases of RxJS as dep

direct dependency : if consumer application relies on v5, can break between your lib (as it carries 2 different version of rx instance) so it could be major.
peer dependency : now your lib will ask consumer application install v6 instead of v5, it also falls back to major (as consumer need to bump their version of rx)

so in my packages (i.e https://github.com/kwonoj/rx-sandbox/releases/tag/v1.0.0) I called it for major bump for exact those reason.

If your lib have proper interop ensures working on v5 & v6 both, then it's definitely not major.

Source https://stackoverflow.com/questions/53023328

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install rx-postmessenger

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: