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
Apparently antlr4@4.9.0 switched over from require to es style exports and imports and changed the location of the code in the packaged module (from ./ to src/). As a result, the type definitions now do not reflect the reality of how the antlr4 types should be imported from the antlr4@4.9.0 module.
Hi thread, we're moving DefinitelyTyped to use GitHub Discussions for conversations the @types modules in DefinitelyTyped.
To help with the transition, we're closing all issues which haven't had activity in the last 6 months, which includes this issue. If you think closing this issue is a mistake, please pop into the TypeScript Community Discord and mention the issue in the definitely-typed channel.
Apparently antlr4@4.9.0 switched over from
require
toes
style exports and imports and changed the location of the code in the packaged module (from./
tosrc/
). As a result, the type definitions now do not reflect the reality of how the antlr4 types should be imported from theantlr4@4.9.0
module.For a related issue in the antlr4 project, see antlr/antlr4#2968.
@types/xxxx
package and had problems.@types
package versions do not follow SemVer.Definitions by:
inindex.d.ts
) so they can respond.The text was updated successfully, but these errors were encountered: