fix: node-tools always using WASI binary #684
Annotations
6 warnings
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v1, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Build and run tests:
extensions/chord.common/Extensions/StringExtensions.cs#L53
Possible null reference assignment.
|
|
Build and run tests:
extensions/chord.common/Extensions/StringExtensions.cs#L58
Possible null reference assignment.
|
|
Build and run tests:
extensions/chord.common/Extensions/StringExtensions.cs#L59
Possible null reference assignment.
|
|
Build and run tests:
Core/Meta/JsonContext.cs#L83
Using member 'System.Text.Json.JsonSerializer.Serialize<TValue>(Utf8JsonWriter, TValue, JsonSerializerOptions)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext, or make sure all of the required types are preserved.
|
Loading