Meteor was first released back in 2011, and since then it’s been one of the most powerful platforms for web developers. It brought many new concepts to the table — one of the more powerful ones is where the client, server and the database can share code, almost the same API and code snippets, which really accelerated the development process.
This has been a very big advantage that’s proven itself to be worthy, but has also created a misconception that
Meteor is a monolith that can’t be broken down to smaller parts. But in fact, when you build a
Meteor app for deployment to Galaxy or any other hosting platform,
Meteor essentially generates a stand-alone Node application that you can run anywhere Node is installed. This built application can be easily consumed by a wide variety other tools that work with Node and Javascript apps.
In this post, I will show how you can use your existing React, Angular, or WebPack front-end app (or break up your existing
Meteor front-end app away from the
Meteor CLI) while still using
Meteor’s benefits like
Meteor Collections, Minimongo, real time updates and DDP, accounts packages and more…
meteor react javascript node