Ivan Dudinov

Hi there! I was struggling for making templating and pre-rendering work together properly, and realized that the order of file processing should be changed. That seemed to me quite hard...

Well, I see Webpack philosophy as a way when some new content/assets produced by plugins, but loaders just transform assets to another representation. Initial idea of `prerender-loader` seems to me...

Hi @Saravanan90 Could you please provide an example of audio tag that you tried to process? And what you get as result

+1, the other possible desired use case is something like that – just use something JS evaluate-able : ``` @require('./header.html', { someValue: 2 + 3, title: (originalTitle && originalTitle.trim()) ||...

OK, I've investigated the sources a bit, and have found out that object literal (used as second `@require` argument) is processed by `JSON.parse` and then by `JSON.stringify` inside the loader,...

A workaround came to me suddenly :) Tricky a bit, and uses portions of the loader's source code as example, but here it is: ```javascript ```

Hi, the thread is quite old but still open, just came across it and wanted to share my solution for the problem of `Template execution failed: ReferenceError: name is not...

Hi there! just sharing another version of a custom solution of the issue. Script for adding/restoring packages: https://gist.github.com/idudinov/ca12ba99f615a23776bed03aa662c29d The idea here is still to use `firebase.json` hooks but with the...

@emaphp thanks for merging and releasing new version!

Hi! Currently I abandoned using import maps (aka path aliases) within `functions` folder and moved all my client-server re-usable code outside `supabase` folder, and it works perfectly both in local...