Stephan Meijer

That was exactly what I was thinking after a quick look, but was really hoping I missed something there. > Let's hide `deprecation` messages. Sounds like a solid plan 😅.

> Delete user functionality (Right of Erasure) Whereby the personal data of the user should be unset in the users collection, but not the general account data. If a user...

> One can request from you to delete all data associated with their user. But what does that mean? Let's have a user named "John Doe" with username "j.do". He...

> onRemoveUser hook - Full user's Object (e.g. MongoDB record) should be passed into this hook, so we can manipulate user's data before it will be erased, like depersonalization Perhaps...

> Though there was a mention that the theory behind this rule is that you can take data from one service and give it to another. I'm not sure if...

A fix would indeed be very welcome. This one is a little frustrating at least. Besides that; awesome library!

This would be really awesome. Have the benefits of both run types. The easy (and reproducible) container from `Source mode`, but still the small final size of the `Pre-bundled mode`.

Can you tell a little about the struggle you've been experiencing? Perhaps sharing the knowledge can lead to a solution.

I might hope that developers will detect "misspelled table names" while they're still actively writing their code. It is unlikely that unwanted tables will be created in a production environment....

In addition to `years of experience: How long you've been writing JavaScript.` I would also like to know how long they have been in the development profession. In 2019 there...