One of our main concerns when making changes in node is how they effect userland. I have recently been working on a codemod (correct-ts-specifiers) to address a pain-point users have with --experimental-strip-types. I realised this can be expanded to ease other userland migrations, such as adopting new features and breaking changes (such as experimental ones prior to reaching stable).
I will be presenting a plan (or possibly an active iniative) for an official nodejs collection of these migrations, their utility to our community, and the general process in facilitating them.
This will include a means for users to easily contribute such migrations (as well as collaborators, perhaps as part of a breaking change or new feature).
I've had preliminary discussions with the maintainers of codemod on what this might look like, and they are onboard to assist/facilitate 🙂
Topic of the session
Code migration
Breaking changes
New feature adoption
Proposal
One of our main concerns when making changes in node is how they effect userland. I have recently been working on a
codemod(correct-ts-specifiers) to address a pain-point users have with--experimental-strip-types. I realised this can be expanded to ease other userland migrations, such as adopting new features and breaking changes (such as experimental ones prior to reaching stable).Userland has already started creating these (ex
node-globmatch-native).I will be presenting a plan (or possibly an active iniative) for an official nodejs collection of these migrations, their utility to our community, and the general process in facilitating them.
This will include a means for users to easily contribute such migrations (as well as collaborators, perhaps as part of a breaking change or new feature).
I've had preliminary discussions with the maintainers of codemod on what this might look like, and they are onboard to assist/facilitate 🙂
Topic of the session
Code migration Breaking changes New feature adoption
Type of the session
Estimated duration of the session
30 minutes (can be less)
Date and Time of the session
Level
Pre-requisite knowledge
Code migration Abstract Syntax Trees (ASTs)
Describe the session
I plan to present a demo and the unfolding plan (it will likely already be in motion by the time the collab summit occurs).
Session facilitator(s), Github handle(s) and timezone(s)
Meeting notes and Virtual Meeting Link
Follow-up / Set-up sessions (if any)
Additional context (optional)