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
Summary: For Express 5.x, support TypeScript by packaging definitions with the project. This is used by TypeScript automatically when you add typings to the package.json. As part of the effort, there needs to be a good CI step and process in place. As the author of @typings, I have plenty of background on solving the issue, but it should be as straight-forward as possible for everyone to be involved.
An initial PR demonstrating TypeScript definitions is available at pillarjs/path-to-regexp#72 and awaiting some review. Integration with CI will be an ongoing topic, the best process is having TypeScript test files which will do type checking and runtime checking. However, the linked issue above is one approach that can also work (comparing what TypeScript knows about the .js package and our hand written .d.ts file).
I'm opening this issue to give heads up and hopefully collaborate on the final solution for Express.js 5.x.
The text was updated successfully, but these errors were encountered:
References: expressjs/express#2818, typings/typings#322, microsoft/TypeScript#7546.
Summary: For Express 5.x, support TypeScript by packaging definitions with the project. This is used by TypeScript automatically when you add
typings
to thepackage.json
. As part of the effort, there needs to be a good CI step and process in place. As the author of @typings, I have plenty of background on solving the issue, but it should be as straight-forward as possible for everyone to be involved.An initial PR demonstrating TypeScript definitions is available at pillarjs/path-to-regexp#72 and awaiting some review. Integration with CI will be an ongoing topic, the best process is having TypeScript test files which will do type checking and runtime checking. However, the linked issue above is one approach that can also work (comparing what TypeScript knows about the
.js
package and our hand written.d.ts
file).I'm opening this issue to give heads up and hopefully collaborate on the final solution for Express.js 5.x.
The text was updated successfully, but these errors were encountered: