Building a real compliance SaaS with Meteor 3.5 + Blaze 3.1 : no jQuery, 99% AI-written

Good experiment ahead with a promising production outcome!

Great that, in the meantime, you’re using the recently published Agent Skills as a form of validation. That input will be really important to keep improving them, and we’ll appreciate PRs around it with the evidence shown.

Rspack tests: have you seen incomplete or empty test bundles on Meteor 3.5 stable, or does this appear fixed in your setup?

Every test file has to be explicitly imported from a client or server test barrel.

Regarding tests, this depends specifically on how your app is configured. If it has a test entrypoint in the package.json file, it will need to be imported from a barrel index file. If that is omitted, it will run eagerly as Meteor has always done. This is also covered by E2E tests in Meteor core. This app for instance doesn’t have testModule described: meteor/tools/e2e-tests/apps/react-router/package.json at devel · meteor/meteor · GitHub

With Rstest, this will be improved further once a new standard for test discovery is enforced, but until then, Meteor’s way of handling them is preserved through the testModule config, with lazy or eager loading depending on its config.

If you find any issues with this, it may be good to cover them one by one in separate issues on the repository. Maybe it’s about updating the docs to make something clearer, improving the AI training, or finding an opportunity to further improve some scenarios.

1 Like