aws / aws/aws-lambda-roadmap

Feature- Node.js including .ts files when searching for handler

オープン
#63 コメント 1 件 リアクション 16 件 担当者 1 名 @jtuliani が担当を希望しています GitHub で見る
主要言語
言語のデータがありません
スター
196
フォーク
5
PR マージ指標
30日以内にマージされた PR はありません

説明

**Note**
> * Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
> * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
> If you are interested in providing additional feedback, please leave a comment

**Description**
Since Node v22.18.0 the node.js loader can load .ts files by default (and since V22.6.0 with the feature flag), that can already be utilized within lambdas.

The only issue is that file including handler still needs to be .{m,c}js file. So to harvest value from running TypeScript natively we need to do workarounds like having index.js file with following:
```javascript
import { handler } from 'actualIndexFile.ts';

export const handler = async (event, context) => await handler(event, context);
```

**Additional context**
* Since underlying Node.js loader is capable of handling the .ts files (from versions mentioned) it should hopefully be small change to also look for .{m,,c}ts files along .{m,c}js when looking for handler from Lambda command.
* Unless bundling is needed, running TypeScript natively provides values like no longer needing source-maps, moving compilation to validation stage of release, unifying tech-stack.

コントリビューションガイド

コントリビューションガイドを開く

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。