Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

September core team meeting notes #649

Merged
merged 2 commits into from
Sep 30, 2024
Merged

September core team meeting notes #649

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4b45b20
September core team meeting notes
joeldenning Sep 30, 2024
867e0af
Fix typo
joeldenning Sep 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions blog/2024-09-30-core-team-meeting-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# September 2024 Core Team Meeting

*Held via Slack*

Attendees: Joel Denning, Ian Bacher, Milan Kovacic

Date: 2024-09-14 through 2024-09-20

## Meeting Agenda

- Discuss the new #paid-support channel in Slack
- Discuss release plan for single-spa@7. [email protected] was released!
- Discuss recommendations from Milan:
- Market positioning by touting support for multiple frameworks
- single-spa helper libraries need more maintainers
- suggestion to move from Slack to Discord, to avoid disappearing messages
- proposal to move to native modules
- improve documentation for common use cases, such as migrations, maintenance of import maps, caching, common deployment stacks, etc
- Discuss recommendations from Joel:
- Possibly support module federation in create-single-spa (back-and-forth discussion about whether to support both module federation and native modules, or only native modules)
- Modify create-single-spa to have an ESM/SystemJS toggle and change it to ESM by default
- Develop [import-map-externals-webpack-plugin](https://github.com/single-spa/import-map-externals-webpack-plugin) that automatically externalizes all dependencies in an import map that’s either on disk or over network.
- Develop a new project or extend and existing one (like jspm) that assembles the files needed for self-hosting esm shared dependencies, and create all the CI/CD tooling necessary to upload the files to a corporate CDN.
Loading