Closed mattmazzola closed 5 years ago
That's odd - thanks for pointing this out. Will check it out.
Doing some much needed old bug cleanup. This does seem to resolved in the latest (1.3.1) version:
export declare const initializeRoutes: (app: express.Express, port: number, botUrl: string, conversationInitRequired?: boolean) => void;
I'm not sure how it could happen as the build process is a simple
tsc
on the src folder, but somehow in the latest 1.2.5 package I'm seeing thebridge.d.ts
file with thisI'm guessing that maybe the latest package was published with stale .d.ts. It has
getRouter
returningany
instead of theexpress.Router
However, when I build the source locally I get the following which looks correct:
I could imagine weird scenario where of the .d.ts exports types depending on express then it should also be declared as a
peerDependency
so consumers have it.