Session Proposal: module loading customization/optimization and CJS/ESM interoperability #422
Description
Proposal
Topic of the session
Discuss recent module loading customization and interoperability efforts
Type of the session
- Collaborate
- Workshop
- Talk
Estimated duration of the session
1h
Date and Time of the session
TBD
Level
- Beginner
- Intermediate
- Advanced
Pre-requisite knowledge
Familarity with module loading in Node.js
Describe the session
Recap and review recent module loading work, brainstorm ideas
- Documenting dual package shipping patterns and updating ecosystem practices: Bootstrapping the initiative: TODOs? nodejs/package-examples#2
- What are some projects that might already be hitting require(esm) that we should check for regressions from unflagging
- What patterns are people using to ship modules
- What else is blocking them from migration to ESM
- What are the practices that are used to migrate
- What else can be done to help
- What kind of content should we put out there, where...
- Missing pieces of ESM
- Performance
- Snapshot & SEA support
- ?
- Synchronous, in-thread & universal module loader cutomization hooks: doc: add synchronous hooks proposal nodejs/loaders#198
- What are the things not supported in module.register() that we can use the new API to fix
- Is sync resolve + sync load + startGraph enough
- deasync for certain workloads
- File-based preload configurations (noderc): Support .noderc or similar file-based initialization configurations? nodejs/node#53787
- What are people using doing for preloaded configurations, what fields should be in there
- What format is deseirable
- Pain points of runtime configurations
- Conflicts with other runtime configurations?
Session facilitator(s), Github handle(s) and timezone(s)
Meeting notes and Virtual Meeting Link
TBD
Follow-up / Set-up sessions (if any)
Additional context (optional)
TBD