Monorepos bring huge advantages for code sharing and consistency, but deploying Firebase Functions from them often leads to E404 Not Found errors or TS6059 TypeScript issues. This occurs because Firebase's isolated build environment doesn't understand local workspace packages or paths aliases.

After navigating the challenges, a robust solution emerged: packing the shared package into a .tgz tarball and using an automated script (predeploy.js) to manage its inclusion during the deployment process. This guide details this specific, working workflow based on a real-world setup.

The Core Problem Recap​

Firebase Functions deployment typically involves:

1. Uploading only the specified functions directory.
2. Running npm install or npm ci based only on the package.json (and potentially package-lock.json) found within that uploaded directory.

This breaks when npm tries to find local workspace packages (like @your-org/common) because they aren't on the public registry and the rest of the workspace isn't present. TypeScript paths pointing to local source can also cause TS6059 (rootDir) errors during builds.

The Solution: Automated .tgz Packing​

This method ensures the shared package is treated like a regular dependency within the deployment package itself:

Kickstart a new project with FireCMS in a single command​

When was the last time you started a new project using a new tool? Can you remember how easy it was?

We are eager to help you start a new project as soon as possible. We want you to fully focus on your project and not on the setup. Allow us to take care of that; all you need to do is:

firecms init

That's it! You are ready to go. You can now start building your project with FireCMS.

FireCMS Flavors​

If you are familiar with FireCMS, you must already know the different flavors we offer: Community, Cloud, or Pro. Or maybe we just confused you a little in the past. No worries, let's recap.

Community​

The classic old-fashioned MIT licensed FireCMS. You can use it for free, forever. It's the perfect choice for small projects or personal use. You handle the hosting; we handle the CMS. Create collections, add authentication, set it up, and after a working build, deploy it to Firebase Hosting or the hosting of your choice.

Batteries included for Firebase Firestore and MongoDB Atlas. Add more than 40 UI components, a custom view, and even our Notion-style Markdown editor. You can customize the CMS to your needs.

If you've been here for a while and you are 100% sure this is your choice, don't be shy and start a new project with:

firecms init --community

Cloud​

The supercharged SaaS version of FireCMS. The amazing editor. And on top of it, add user management, roles, permissions, a UI-based collection editor, search, autocomplete based on LLMs, customization, App Check, multiple database support, unlimited collections, users, extra customization with code... And the list could go on for a while.

FireCMS: Open Source at Heart​

Soon we will release an updated CLI that will make it easier to start a new project, in the different flavors of FireCMS.

FireCMS was born as an open-source software project, and our plans are to keep it that way. We believe in the power of open source and the community surrounding it. We are committed to building a product that is not only useful but also transparent and accessible to everyone.

We want to take a moment to share our plans regarding licensing, open source, and next steps.

The FireCMS Multiverse​

From the first version up to today, we have been working on different versions of providing services based on FireCMS. You may be familiar with the Pro or Cloud versions. Also, most of our code is public, but not all of it is open source, as some packages use a different license.

Yes, we experience fragmentation, similar to Android. Let's take a look at these versions and clarify them. Basically, FireCMS 3.0 comes in several flavors.

FireCMS Community​

The core of FireCMS has an MIT license. Use it as you wish, with the freedom to modify and distribute. This is how we started, and we will keep it that way.

A TypeScript library built on top of React to manage data in Firestore forms the foundation of all other versions.

Do You Need a No Code Tool for Firebase?​

This article was initially titled "No Code Tools for Firebase." We already knew some tools, but as we delved into the research, we decided to drop the title—and the idea. You probably don't need a No Code tool for Firebase. So instead of a benchmark, welcome to the most opinionated article about Firebase and No Code tools.

Firebase and Firestore​

Firebase is one of the greatest products built for developers. Based on Cloud Services, it features a Serverless architecture that allows you to focus on building your product without worrying about the underlying infrastructure. So you have:

• Firestore: a NoSQL database to store your data in the cloud.
• Functions: a serverless function that allows you to run your code in response to events.
• Authentication: a secure authentication system.
• Storage: a secure file storage system.
• Hosting: a web hosting service that allows you to deploy your static files.
• Messaging: a messaging service that allows you to send push notifications to your users.
• A/B Testing, Remote Config, and many more services.

It gained a lot of popularity among mobile app developers. Here is our easy-to-integrate Backend as a Service with Authentication and File Storage. Simple to use and easy to integrate. Outstanding.

Is your value proposition building an Authentication system, Storage, or Backend? Have a seat and build your product. That's the idea.

Firebase in Your Tech Stack​

So, you decided to use Firebase to build your product. That usually means you are a developer or have an internal development team. The first decision is made. I am building a React App, so I am going to use Firebase for the Backend.

In the rapidly evolving landscape of content management systems (CMS), choosing the right backend is more critical than ever. Developers are faced with a plethora of options, from traditional setups like WordPress to modern headless CMSs like Strapi, Contentful, and Sanity. At FireCMS, we've embraced Firebase as the backbone of our CMS, and in this article, we'll delve into the benefits of using Firebase over other CMS backends. We'll also provide direct comparisons to alternative CMSs to help you make an informed decision.

The Firebase Advantage​

Firebase, a platform developed by Google, offers a comprehensive suite of tools for app development. It provides:

• Cloud Firestore: A flexible, scalable NoSQL cloud database for storing and syncing data in real time.
• Authentication: Secure and easy-to-use authentication services supporting email and password, phone auth, and social logins.
• Cloud Functions: Serverless framework to run backend code without managing servers.
• Hosting: Fast and secure web hosting for your web app, static and dynamic content.
• Realtime Database: A real-time, low-latency database for mobile, web, and server development.

By leveraging Firebase, FireCMS offers a CMS that is not only powerful but aso scalable, secure, and cost-effective.

The sleek and intuitive FireCMS dashboard powered by Firebase.

OpenSource, The Good, the Bad, and the Ugly​

Open source is a hot topic right now. Often making headlines due to high-profile conflicts like the recent WordPress vs. WP Engine dispute over plugin licensing disagreements, or Elastic's licensing battle with AWS, which led to a shift to a source-available license. These incidents underscore the complex landscape of open-source development, a journey we've been navigating since our initial commit on GitHub in April 2020.

Since its inception, FireCMS has evolved from an internal tool to a widely-used open-source content management system (CMS) that helps developers build and prototype products efficiently. We want to share our experiences; the good, the bad, and the ugly of building FireCMS in public with an open-source license.

The Good​

Our journey with FireCMS began as an in-house solution to streamline our development process. Seeing it grow beyond our organization and being utilized by other projects and companies has been profoundly fulfilling. It not only helped us in building and prototyping products faster but also empowered others to do the same.

The first time I saw the Stripe shader animation on their website, I was hooked. I really wanted to have something that cool for the websites I was working on and tried to reverse engineer what Stripe does. I must say, it wasn't easy! I had to learn a lot about shaders, WebGL, and three.js to get to the point where I could create something similar.

We are going to be using a lot of Perlin noise functions to generate the waves and the gradient. Perlin noise is a type of gradient noise used in computer graphics to create natural-looking textures. It was invented by Ken Perlin in the 1980s. The noise is generated by interpolating between random values. It is locally stable, so it is well-suited for generating animations by including a time parameter in the noise function.

The Stripe animation is really a 3D shape, a plane divided in triangles acting like a flag that has waves passing through it. On top of that, there is a gradient that changes color and brightness. That is really the essence of the effect.

Check what's new in your favourite CMS

We are excited to announce the release of FireCMS Beta.9. This release includes a lot of new features and improvements, including a new Markdown editor, multi select, and MongoDB support.

FireCMS continues its journey to become the most flexible and powerful CMS. We aim to become a true headless CMS, with and by headless we mean compatible with any database and backend, as well as also detached from any frontend technology.

New Markdown editor​

Completely revamped Markdown editor inspired by Notion, with an amazing UX and autocomplete features. The previous editor was not very user-friendly, and we have decided to replace it with a new one that is more powerful and easier to use. It is also now possible to upload images inline. The editor can be used as a Markdown field in your collections, as well as a standalone component in your components.

Multi select​

We have improved the multi select component, now supporting search and better performance. The previous version would clip items based on the position of the dropdown, which was not ideal.

MongoDB support​

FireCMS continues to expand its database support. We have added a new package @firecms/mongodb that allows you to connect to MongoDB databases.

You can now run FireCMS PRO with MongoDB as your backend, with no connection to any Firebase services. Use the Auth and Database services of MongoDB Atlas to authenticate and store your data.

This is part of our efforts to bring all the power of FireCMS with the PRO version to any database you want.

Say Hi to MongoDB!​

For FireCMS users, connecting to MongoDB just got a lot easier. While FireCMS has always offered the flexibility to integrate with various databases, we're thrilled to announce a dedicated package for seamless MongoDB integration.

How easy? npm easy npm install @firecms/mongodb, or yarn easy yarn add @firecms/mongodb.

This is part of our efforts to bring all the power of FireCMS with the PRO version. The most advanced and flexible version of FireCMS.

Why MongoDB?​

Choosing the right database is crucial, and MongoDB, especially when paired with its cloud counterpart Atlas, presents a compelling option for many projects. Its document-oriented structure aligns well with how we often model data, and its performance and scalability make it suitable for projects of all sizes.

Same FireCMS Experience, Now Powered by MongoDB​

We implemented the necessary utilities to connect and consume Atlas MongoDB database and authentication services.

If you are working on any kind of public-facing digital project —no matter if it's a website, a web app, a mobile app or desktop app — you will likely need a Content Management System. There are a lot of options to chose from, and different solutions are better suited for some needs than others. We can distinguish some categories straight away:

• General purpose or web oriented
• Headless or traditional
• By access to data APIs (GraphQL, REST, SDKs)
• Cloud based or self-hosted

We are building this guide to help you pick the right CMS for your project. We will be updating it regularly, so make sure to check back often.

One of the motivations for this guide is to help users understand the differences between CMSs. Despite creating FireCMS, we are not trying to promote it as the best solution for everyone. We are just trying to help people understand the trade-offs of different solutions. This is the same thing we say to our users when they ask us for advice on what solution to use.

General purpose or web oriented​

The first thing to consider is whether you need a general purpose CMS or a web-oriented one. A general purpose CMS is a tool that can be used to manage content for any kind of project (apps, desktop, web), while a web-oriented CMS is a tool that is designed to manage content for websites.