dmudro

[Vercel / AWS Lambda have now made Node.js v16 available](https://vercel.com/changelog/node-js-16-lts-is-now-available) which in my experience provides the ultimate fix for the issue here. I am not sure about the discussion around...

following up on the source of this issue, updating to latest pdfjs-dist creates more syntax error issues, this time client side in older browsers as their bundle uses private field...

regarding my earlier suggestion and some others here, you can totally get around the latest JS syntax and Node js version by simply importing the legacy version i. e. `pdfjs-dist`...

There is a cleaner workaround without compromising security. By forking the select2 templates and providing the path as custom theme in the config, the ng template engine will pick up...

1. how do you localise email subject with the template? 2. as an alternative... is it possible to disable emailing in cloud Supabase completely so I'd handle all email flows...

> Just to get a sense of what languages people are looking for @J0 any language / locale really. as @kvetoslavnovak pointed out just in the EU there 20+ options.

@phuoc-ng sounds good in theory but if you follow [your guide](https://webpack.js.org/plugins/copy-webpack-plugin/#copy-in-new-directory), there are some Next.js specificities probably not compatible with the suggested solution for "pure webpack". Namely this part of...

Cheers @raibima, I tried [asset modules](https://webpack.js.org/blog/2020-10-10-webpack-5-release/#asset-modules) as suggested with some tweaks around `node_module` path: ``` const workerUrl = new URL('node_modules/pdfjs-dist/build/pdf.worker.js', import.meta.url); // no ../node_modules ... ``` **Next.js 11** Webpack 5...

Alright. I'll revisit to make sure I didnt have something locally conflicting with asset modues and will report back here if I find out anything.