hazelcast-nodejs-client
hazelcast-nodejs-client copied to clipboard
About EntryListener.d.ts compilation error [API-1417]
There is known issue when "strictNullChecks" is true in typescript configuration. You will get an error in EntryListener.d.ts like the following:
node_modules/hazelcast-client/lib/proxy/EntryListener.d.ts:14:5 - error TS2411: Property 'mapEvicted' of type 'MapEventListener<K, V> | undefined' is not assignable to 'string' index type 'EntryEventListener<K, V> | MapEventListener<K, V>'.
14 mapEvicted?: MapEventListener<K, V>;
~~~~~~~~~~
node_modules/hazelcast-client/lib/proxy/EntryListener.d.ts:15:5 - error TS2411: Property 'mapCleared' of type 'MapEventListener<K, V> | undefined' is not assignable to 'string' index type 'EntryEventListener<K, V> | MapEventListener<K, V>'.
15 mapCleared?: MapEventListener<K, V>;
~~~~~~~~~~
Found 9 errors in the same file, starting at: node_modules/hazelcast-client/lib/proxy/EntryListener.d.ts:7
This issue will be fixed in the following releases but to workaround the issue you can set "skipLibCheck" to true in your typescript configuration.
{
"compilerOptions": {
"strict": true,
"skipLibCheck": true
}
}
{
"compilerOptions": {
"strictNullChecks": true,
"skipLibCheck": true
}
}
Related issues:
- https://github.com/hazelcast/hazelcast-nodejs-client/issues/1316
- https://github.com/hazelcast/hazelcast-nodejs-client/issues/1286
Internal Jira issue: API-1417
Fixed by: https://github.com/hazelcast/hazelcast-nodejs-client/pull/1294 Closing.
@yuce this is fixed but the issue still happens unreleased branches. maybe it is a good idea to keep the issue until every maintenance release is released