Ben

Thanks for reporting this issue. I've come across this error a few times in the past few weeks & am yet to find an exact cause other than some fault...

I have tried but I am unable to reproduce this locally, no is CD showing this issue. Are you able to re-install your `node_modules` to verify it's not a outdated...

Currently experimenting setting up a system using a custom subdomain (`app.example.com`) & ran into this same issue. Unsure if it will fix / help others but I got mine working...

Is there any good examples of Firestore rules to use that are safe & work as intended? Or at least some guidelines / tips on how to create a ruleset...

Thanks for all the replies. I am aware you can just change your config extension to end in `.ts` or `.tsx` & add a JSDoc type comment but I was...

100% agree. Found this via the GitHub trending page and I'm so happy I did. Already planning on creating multiple configs for both local machine management as well as managing...

If more information is required, link to repository can be found here: [github.com/Meadowcottage/KaplanSays](https://github.com/Meadowcottage/KaplanSays). The dist files was made in the order provided by the [deploying to heroku using node.js](https://github.com/yeoman/generator-webapp/blob/master/docs/recipes/node-heroku.md) recipe....

I have been looking into this more and I found the issue. The Heroku app by default tries to build from the root directory. Makes sense about the no script...

I don't have a huge total use time with Heroku, but from what I have been working out is that you can instead point it to a branch to deploy...

Agreed. Also getting this. Fresh install and generates no content at all.