sitemap.js | Sitemap-generating framework for node.js | Sitemap library

As you noted, this isn't scalable and your costs are going to skyrocket since you pay per read/write on Firestore, so I would recommend rethinking your architecture.

I solved a similar problem several years ago for an App Engine website that needed to generate sitemaps for millions of dynamically created pages and it was so efficient that it never exceeded the free tier's limits.

Step 1: Google Storage instead of Firestore

When a page is created, append that URL to a text file in a Google Storage bucket on its own line. If your URLs have a unique ID you can use that to search and replace existing URLs.

Try adding "type": "module" to your package.json.

I used a custom sitemap generator like:

fs.writeFileSync doesn't write file in UTF-8

Actually it did. US-ASCII is a subset of UTF-8 for characters with a character code 127 and below. So, it's both US-ASCII and UTF-8.

For plain ascii characters below 127, there is no physical difference between UTF-8 and US-ASCII. US-ASCII characters encode to themselves in UTF-8.

A file like you're writing doesn't typically record what character set it is. It's up to the reading software to either infer the encoding from the data it finds or use other clues such as the file extension to guess. So, your program is just telling you that your file meets all the requirements of US-ASCII and thus looks like US-ASCII which happens to be a subset of UTF-8.

Put some Japanese characters in there and it will look different since they don't fit into US-ASCII. They will use multiple bytes to encode properly.

You will need 2 different webpack configs, pass command line arguments like the below:

webpack --env.browser=chrome --open 'Google Chrome'

webpack --env.browser=other --open safari

And maintain 2 different webpack configs in webpack.chrome.js and webpack.other.js

and put this in webpack.config.js

I was able to match using another .use for the route using the extension.