chore: minutes for 2024-11-20 #19
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Nov 20, 2024
AugustinMauroy
approved these changes
Nov 20, 2024
|
Closes #18 |
meetings/2024-11-20.md
Outdated
Comment on lines
32
to
40
| Marco: No need to support it for the unflagging, it can wait. | ||
| Daniel: Right now don’t think it’s a good idea, but not definitive. | ||
| Jacob: use engines section of package.json to mitigate some the incompatibility issues | ||
| Marco: probably enable it behind a flag | ||
| Daniel: monorepo use symlinks so don’t need it | ||
| Andrew: monorepo already work, maybe does not work when publishing .ts files internally | ||
| Daniel: If users wants to use workspaces, that is already documented | ||
| Jacob: monorepo in fact works, tested in codemod | ||
| Marco: We believe monorepo use-cases should all work, we will re-evaluate after the feature becomes more stable. |
There was a problem hiding this comment.
This does not format correctly in markdown (it collapses into a single continuous paragraph), but I don't know how to get it to do so.
meetings/2024-11-20.md
Outdated
Comment on lines
43
to
53
| Jacob: Is volunteers to document how to publish a typescript package on npm | ||
| Daniel: ts 5.7 landing tomorrow | ||
| Daniel: About the ack from TypeScript team, exciting, the missing piece is providing errors in the IDE but no blockers. | ||
| Marco: transform types might always stay behind a flag, source maps should not be enabled by default. Marco should we wait to unflag, for a TS compatible flag? | ||
| Daniel: Not a big deal, it’s ok | ||
| Conclusion: TS team are ok with unflagging | ||
| TS Issue for option to disallow features requiring transformations which are not supported by Node.js' --strip-types: <https://github.com/microsoft/TypeScript/issues/59601> | ||
| Andrew/Daniel: The plan is for TS to add the lint flag in TS 5.8 (the next release) | ||
| Marco: Documentation was added: <https://nodejs.org/docs/latest/api/typescript.html#type-stripping> | ||
| Marco: Talking about next steps, should we ping frontend frameworks? | ||
| Daniel: Would be good but not necessary |
There was a problem hiding this comment.
Same here: collapses into a single paragraph
56e61af to
3f44875
Compare
|
@JakobJingleheimer why your approval is gray? 🤔 |
|
I think I have only read-write permissions on the repo (I think anything lower than |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #18
@nodejs/typescript