Neat. I am using ES modules instead of requirejs and that works decently well. I found 3 downsides to this approach:
adding new components etc is a few lines of manual work (acceptable)
CSS cannot be scoped without using lit-element components (acceptable)
npm packages that are not ESM ready need a simple conversion (mildly inconvenient)
For non-production, or light hobby websites, I find this perfectly acceptable, and I really prefer being able to edit html/js without heavy building that takes hundreds of megabytes of disk space. This way I can also use my custom Node.js server without having to wrestle with Nuxt or similar, but of course, to each their own.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Neat. I am using ES modules instead of requirejs and that works decently well. I found 3 downsides to this approach:
For non-production, or light hobby websites, I find this perfectly acceptable, and I really prefer being able to edit html/js without heavy building that takes hundreds of megabytes of disk space. This way I can also use my custom Node.js server without having to wrestle with Nuxt or similar, but of course, to each their own.