Skip to content

Commit 0d9f8b4

Browse files
marco-ippolitoJakobJingleheimer
authored andcommitted
chore: add minutes from 2024-12-18
1 parent 47ad487 commit 0d9f8b4

File tree

1 file changed

+50
-0
lines changed

1 file changed

+50
-0
lines changed

meetings/2024-12-18.md

+50
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
# Node.js TypeScript team Meeting 2024-12-18
2+
3+
## Links
4+
5+
* **Recording**: <https://www.youtube.com/watch?v=BX_ewVG1lyg>
6+
* **GitHub Issue**: <https://github.com/nodejs/typescript/issues/21>
7+
8+
## Present
9+
10+
* Typescript team: @nodejs/typescript
11+
* Marco Ippolito: @marco-ippolito
12+
* Rob Palmer: @robpalme
13+
* Jacob Smith @JakobJingleheimer
14+
* Augustin Mauroy @augustinmauroy
15+
16+
## Agenda
17+
18+
## Announcements
19+
20+
Jakob: codemod for migration to strip types almost read, should be released soon
21+
22+
* Extracted from **typescript-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
23+
24+
### nodejs/nodejs.org
25+
26+
* Expand CODEOWNERS to each learn section owner/advocate [#7292](https://github.com/nodejs/nodejs.org/issues/7292)
27+
28+
Augustin: Website team would like to add @nodejs/typescript as codeowner of the typescript content of the website for review
29+
Marco: no issue with that, we are already doing it to some degree
30+
Jacob is working on a guide this weekend. Publishing TypeScript: <https://github.com/nodejs/nodejs.org/pull/7279>
31+
32+
### nodejs/typescript
33+
34+
* Unflag `--experimental-strip-types` [#17](https://github.com/nodejs/typescript/issues/17)
35+
Marco: issue with –eval, unflagging –experimental-strip-types would cause a breaking change in case Node.js was fed with invalid syntax.
36+
Created a PR to keep the current behavior and added explicit input types for typescript syntax
37+
<https://github.com/nodejs/node/pull/56285>
38+
This should make unflagging possible.
39+
Before unflagging we should create some content on how to publish TypeScript packages, some part of it was done by the TypeScript team. It’s also important to document decision making about `node_modules`.
40+
Augustin: should we mention in the guide, to publish as `esm` or `cjs` or both?
41+
Marco: we should link back to Jakob article on js publishing article, it should be linked but more focused on the ts side rather than general.
42+
Marco: The item on the issue about frontend metaframeworks is currently irrelevant because we don’t allow type stripping in node_modules so they still have to go through a transpilation step.
43+
44+
## Q&A, Other
45+
46+
## Upcoming Meetings
47+
48+
* **Node.js Project Calendar**: <https://nodejs.org/calendar>
49+
50+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.

0 commit comments

Comments
 (0)