Mainly in that maintaining it can become an issue... also, if you exceed a certain size it won't be indexed, so you'll have to reference other sitemap files, and/or generate them. I've found you're far better off ensuring only the recent endpoints that are updated since the last google scan are about best. And even then, google (and bing) will do a good job at natural discovery. The sitemap really only allows for those sites with frequent publication to be checked more often by google. If you are doing less than a couple posts a day, there's very little reason to worry about it.
When creating a site with ads, wrap your placeholder with an "ad" class, and define the demensions. Also, make sure that it renders well with `.ad { display:none !important;}` set so that you work well with ad blockers.
When working on injecting ads/content, don't use heavy frameworks like jquery, stick to micro frameworks or preferably hand-craft what you need and use rollup to build/bundle. http://microjs.com/ is your friend on this one. If you can come in under 5kb for js+gz, that's your best bet here.
AFAIK optional chaining and the nullish coalescing operator are not in any browser or in Node 12. I'm am using a babel transform for it in my web projects. Also, I believe TypeScript has added support, so you get it there.
Nice little library... probably a great option for adding dynamic elements to server-rendered content, where you might otherwise reach for jQuery (or Knockout).
Just a minor note... You probably want to stick to the most recent 100 entries by last modified date and let any search engine navigate/remember the rest. Inflating the sitemap too big can work against you.
One thing to mention... If you're using AWS Lambda in particular, just use the largest option, you'll usually save enough time to overcome the extra cost as you get more compute with the added memory. Also, if your job *might* take more than 3 minutes, then Lambda is a risk as iirc there's a 5 minute max.
When creating a site with ads, wrap your placeholder with an "ad" class, and define the demensions. Also, make sure that it renders well with `.ad { display:none !important;}` set so that you work well with ad blockers. When working on injecting ads/content, don't use heavy frameworks like jquery, stick to micro frameworks or preferably hand-craft what you need and use rollup to build/bundle. http://microjs.com/ is your friend on this one. If you can come in under 5kb for js+gz, that's your best bet here.I'd probably add/follow a bit about BigInt[1] and Date[2] objects... Probably bringing mention to Object.prototype.valueOf(). [1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt [2] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date