Cool.. would be cool if react components were supported... I've leaned so heavily on material-ui the past few years, I'd rather not go without it. Though bootstrap is easy enough to integrate with just the (S)CSS from source.
When creating a crypto key from a known value would use pbkdf2 @ 10000 or higher iterations for the encryption key from known key, MD5 is *NOT* sufficient.
When an IV or salt is used, it should be unique to each encode. Can be added to the encrypted output or stored separately... re-using the IV allows for a broader attack surface, especially if the encoded content is simlar, such as JSON encoded objects, etc.
Didn't notice it called out, but Brotli in time to compress is roughly the same as .gz, pest to use it for pre-compressed files at build-time, not dynamic compression at runtime (unless the server will compress/cache the results), not good for dynamic routes.
IMHO, this is emphatically *NOT* the most scalable app architecture... imo, feature oriented structures work far better. A given feature may have child features, may have action creators, reducers, components, data access requests, etc, etc.
Nested, mirrored trees organized by type is much harder to work with in practice as your related items are spread across several directories reducing the usefulness of having a directory tree for your files to begin with.
As to the mention of Axios... just wrap fetch for your needs directly.
*REALLY FUCKING SLEAZY*
This was a re-upload of content originally from 2 years ago in JSConf EU 2018. I changed the link to the original content.
About half of erisanakorede's posts have been removed as posted, Hence the Youtube discussion a couple days ago. Next spammy/scammy thing the person posts, deleting the user (which unfortunately removes useful posts, but unsure how much are even original content after this).