Blaze Usergroup Meetings 2026

blaze
21

Looks like 4th June it is :slight_smile:

22

oh, 4th June is a holiday for me and 3pm utc is the lunch time lol, but iā€™ll do my best to be present

btw, I created a public calendar for those meetings, let me know if you can attach it in your calendar and if the meeting schedule is in the proper hour for your timezone, iā€™m still learning how it works

Click here to be redirected to the calendar

itā€™s good to see this user group having another meet, itā€™s an inspiration for what is being discussed in this PR

1 Like
23

Quick reminder, tomorrow is the next Blaze Usergroup meeting. Here is my proposed lightweight agenda:

  1. Recap of 3.1.0 development
  2. Last remaining steps and TODOs for 3.1.0
  3. Whatā€™s coming for 3.2.0
  4. Refining vision for 4.0.0

It would be great to see at least the contributors of 3.1.0 @dupontbertrand @wreiske and of course anyone interested in the future of Blaze @marklynch @harry97 @DanielDornhardt

5 Likes
24

Iā€™ll be there! Added to my calendar just now. :rocket:

1 Like
25

We will meet in the Blaze audio channel on the Meteor Lounge Discord, just scroll down there is a ā€œBlazeā€ audio/video channel:

image

1 Like
26

w are starting just now :rocket:

27

The meeting invite was for a google meetā€¦ I donā€™t have a discord on my work device. Iā€™ll have to make it to the next one!

Screenshot 2026-06-04 at 8.07.42 AM
Screenshot 2026-06-04 at 8.07.42 AM2650Ɨ1800 241 KB

28

Here is the recording:

4 Likes
29

Meeting Minutes: Blaze Usergroup Meeting Q2 2026

Source: Blaze Usergroup meeting Q2 2026

1. Meeting Overview

  • Topic: Recap of Blaze 3.1 progress, upcoming plans for Blaze 3.2, and the long-term vision for Blaze 4.x and beyond [00:14].
  • Key Participants: Host, Bertrand, and Jan.

2. Blaze 3.1 Recap & Next Steps

  • Merged Updates: 8 PRs have been successfully merged. Major improvements include the removal of external npm dependencies and the introduction of a native DOM backend. This allows Blaze to operate completely without jQuery [01:26]. These are currently considered non-breaking changes.
  • Pending PRs: There are 2 pull requests remaining:
    • A visual error indicator that warns developers about missing templates during development [02:17].
    • A fix for stale re-renders for ā€œeachā€ items during sequence updates [06:59].
  • Testing & Reviews: The host emphasized the need for community help with code reviews and testing, particularly for reproducing and testing the stale re-renders fix [03:30].
  • Release Plan: The team decided to contact the Meteor Core team to issue a Beta release right away. This will allow the community to test the current state easily via the package manager [10:45]. Once the remaining 2 PRs are reviewed and merged, a Release Candidate (RC) will be published before the final 3.1 rollout [11:57].

3. Planning for Blaze 3.2

  • Upcoming Features: Development will heavily focus on adding inline expressions, enhancing Spacebars (contributed by Bertrand), and implementing server-side template rendering [12:51].
  • Housekeeping & Backlog: During the call, the team actively organized the backlog, closing resolved issues (such as moving the codebase to ES2015 and removing jQuery) and appropriately linking open PRs [15:17].
  • Benchmarks: The team agreed that implementing better performance benchmarks for Blaze will be an important goal for version 3.2 [17:16].

4. Long-Term Vision (Blaze 4.0 & 5.0)

  • Blaze Standalone: The team discussed the complex goal of decoupling Blaze from Meteor Core (e.g., Tracker, Reactive variables, Reactive dictionaries).
    • Blaze 4.0 is projected to act as an ā€œuntanglingā€ compatibility release [22:04].
    • Blaze 5.0 aims to be a fully standalone tool released on npm [22:23].
  • Developer Experience (DX): To ensure Blaze remains relevant in modern web development, the team highlighted two major future needs:
    • IDE Support: Current IDE support is lacking compared to frameworks like Vue. Improving this will boost developer productivity [28:59].
    • Single File Components (SFC): There is strong interest in adopting a single-file format (similar to Vue) to cleanly scope HTML and JavaScript together in one view file [31:45].

5. Action Items & Next Meeting

  • Action: The host will coordinate with the Meteor Core team to publish the Blaze 3.1 Beta release [10:52].
  • Action: Bertrand will scaffold a small test application to help developers reproduce and review the stale re-renders bug [07:59].
  • Action: Meteor Core team will need to review and merge server-side rendering PRs to unblock Blaze 3.2 features [36:09].
  • Next Meeting: The next Blaze Usergroup meeting is scheduled for Q3 2026 [36:41].
1 Like