@aspnet/signalr - npm Package Compare versions

Comparing version 1.0.26 to 1.0.27

dist/cjs/index.js

@@ -7,3 +7,3 @@ "use strict";
 /** The version of the SignalR client. */
-exports.VERSION = "1.0.26";
+exports.VERSION = "1.0.27";
 var Errors_1 = require("./Errors");
@@ -10,0 +10,0 @@ exports.HttpError = Errors_1.HttpError;

dist/esm/index.js

@@ -5,3 +5,3 @@ // Copyright (c) .NET Foundation. All rights reserved.
 /** The version of the SignalR client. */
-export var VERSION = "1.0.26";
+export var VERSION = "1.0.27";
 export { HttpError, TimeoutError } from "./Errors";
@@ -8,0 +8,0 @@ export { DefaultHttpClient, HttpClient, HttpResponse } from "./HttpClient";

package.json

 {
   "name": "@aspnet/signalr",
-  "version": "1.0.26",
+  "version": "1.0.27",
   "description": "ASP.NET Core SignalR Client",
@@ -5,0 +5,0 @@ "main": "./dist/cjs/index.js",

README.md

 JavaScript and TypeScript clients for SignalR for ASP.NET Core
 
+> :warning: This package will no longer be supported starting August 21, 2021. This package follows the [.NET Core 2.1 support lifecycle](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) which is ending soon. Please transition to using [@microsoft/signalr](https://www.npmjs.com/package/@microsoft/signalr) as described below.
+
 > Note: The JavaScript and TypeScript clients for SignalR for ASP.NET Core have been moved to [@microsoft/signalr](https://www.npmjs.com/package/@microsoft/signalr). If you are already using `@aspnet/signalr` and are unsure when to move to `@microsoft/signalr`, check the [Feature Distribution](https://docs.microsoft.com/en-us/aspnet/core/signalr/client-features) chart in the ASP.NET Core SignalR documentation. Newer client releases are compatible with older version of ASP.NET Core SignalR which means it is safe to upgrade the client before upgrading the server.
@@ -4,0 +6,0 @@

New alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Fixed alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

1200105

increased by0.03%

Number of lines in readme file

60

increased by3.45%

No dependency changes