Project Structure and Module Development in Meteor.js
summary
The talk examines structuring Meteor.js projects and building modules to avoid fragile file-load behavior (filesystem order and alphabet-dependent loading). It compares three module strategies—splitting by execution context (server/client/public), a modules/ folder convention, and full Meteor packages—showing that packages provide explicit load order and exported APIs via package.js (api.use/api.export, api.addFiles). Examples include wrapping Mongo collections with transform into classes and notes on scaling, using React/Angular, and deploying with Galaxy/hibernate.
AI-written summary · about
chapters (8)
- 0:00Meteor.js intro
- 3:05Messy Meteor problems
- 6:18Modular structure
- 8:07Module packages
- 10:32Collections and MiniMongo
- 11:43Meteor drawbacks
- 14:15Meteor’s plans
- 16:02Conclusion & Q&A
related talks
37mMeteor - A Full Stack Framework For Building Pure JavaScript Apps
39mMeteorJS as a framework for hyper prompt development
43mMeteor - What is it, and should I use it or not?
35mRadically faster web development -- Meteor after one year
19mModularity Matters
41mThe future is modules not frameworks. JS modules Architecture demo.
10mMatt Debergalis and Emily Stark (Meteor) interviewed at Fluent 2014
04mDevelopment of JavaScript applications
