search

nodeshift / nodejs-reference-architecture

The Red Hat and IBM Node.js Reference architecture. The teams 'opinion' on what components our customers and internal teams should use when building Node.js applications and guidance for how to be successful in production with those components.
https://nodeshift.dev/nodejs-reference-architecture/
Apache License 2.0
1.66k stars 120 forks source link

Initial draft of typescript guide #74

Closed domharries closed 2 years ago

domharries commented 3 years ago

First draft of typescript article, still some TODOs

roastlechon commented 2 years ago

@domharries the documentation you linked (https://www.typescriptlang.org/tsconfig#esModuleInterop) was very useful information I think we should include here.

Basically what I'd like to try and get across is that for module development, it may be useful to note certain restrictions if developing fully in TypeScript or maybe having a hybrid where its 99% TypeScript and 1% shim files to convert modules that are not pure TS supported (without esModuleInterop flag). Im open to thoughts on how others may want to approach from module authoring perspective.

wtrocki commented 2 years ago

Before we merge we need to add index to the header as in other files on the master.

mhdawson commented 2 years ago

@wtrocki you mentioned you could add the index to the header.

mhdawson commented 2 years ago

Just for context this was updated to address the comments and it was agreed in the last Ref Arch working meeting that it was ready to day.