WebGL(2) context methods don't allow null for resource parameters about typescript HOT 2 OPEN

TypeScript frequently forbids code that would be valid according to specification. The question to ask is: Would people consider it a potential bug in their code if they pass in null? I'd say yes.

from typescript.

In library-authored code, I would agree, but it's of a native API we are talking about. And, as I pointed out, the official wiki recommends not to check for null on resource creation because the API is meant to support null values in place of resources.

You should really only get null from these functions if the context is lost and in that case there’s no reason to check. WebGL is designed so that for the most part everything just runs as normal even when a program or shader is null.
khronos.org --- https://www.khronos.org/webgl/wiki/HandlingContextLost#Don%E2%80%99t_check_for_null_on_creation

So because the type definitions from lib.dom don't include null for the methods accepting resources or null (in the example shaderSource, compileShader, typescript raises errors on code which is recommended on the official doc.

from typescript.