You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experimenting with asciidoctor.js in Deno, and Deno happens to reject running a .ts file that has type checker errors in it (even if the program would execute just fine). If I try to pass a runtime configuration object, I get Expected 0 arguments, but got 1. [2554] as a typechecker error.
... and this executes, and the expected configuration is shown in asciidoctor.getRuntime(), so I believe my assessment is correct that this is just a problem in the type definition:
I think there may be a similar type definition issue with import Asciidoctor from 'asciidoctor'; Asciidoctor() (using the non-namespace-prefixed package), as this results in This expression is not callable. Type [...] has no call signatures. [2349] -- and can be similarly worked around by casting to any. But I haven't done enough testing on how this works with vanilla tsserver in Node to be sure that this isn't a Deno-specific issue (rel. Run the tests suite against Deno #981).
The text was updated successfully, but these errors were encountered:
I'm experimenting with asciidoctor.js in Deno, and Deno happens to reject running a .ts file that has type checker errors in it (even if the program would execute just fine). If I try to pass a runtime configuration object, I get
Expected 0 arguments, but got 1. [2554]
as a typechecker error.I can work around this with some fancy casting, e.g.
... and this executes, and the expected configuration is shown in
asciidoctor.getRuntime()
, so I believe my assessment is correct that this is just a problem in the type definition:asciidoctor.js/packages/core/types/index.d.ts
Line 3732 in d333b7b
Two additional notes:
runtime.framework
is supposed to do, so this definitely is not a blocker in any way, but I think it could use some explanation in https://docs.asciidoctor.org/asciidoctor.js/latest/setup/runtime/import Asciidoctor from 'asciidoctor'; Asciidoctor()
(using the non-namespace-prefixed package), as this results inThis expression is not callable. Type [...] has no call signatures. [2349]
-- and can be similarly worked around by casting toany
. But I haven't done enough testing on how this works with vanilla tsserver in Node to be sure that this isn't a Deno-specific issue (rel. Run the tests suite against Deno #981).The text was updated successfully, but these errors were encountered: