Detected the use of custom TypeScript modules and namespaces JS-0337
Anti-pattern
5 months ago
—
5 months old
ES2015 module syntax is preferred over namespaces
22
23declare global {
24 // eslint-disable-next-line no-unused-vars
25 namespace JSX {26 // eslint-disable-next-line no-unused-vars27 interface IntrinsicElements {28 "hanko-auth": HankoAuthElement;29 }30 }31}
32
33const HankoAuth = ({ api, lang = "en" }: Props) => {
Description
Custom TypeScript modules (module foo {}) and namespaces (namespace foo {}) are considered outdated ways to organize TypeScript code. ES2015 module syntax is now preferred (import/export).
This rule still allows the use of TypeScript module declarations to describe external APIs (declare module 'foo' {}).
Bad Practice
module foo {}
namespace foo {}
declare module foo {}
declare namespace foo {}
Recommended
declare module 'foo' {}