Giuseppe Piccinni
Giuseppe Piccinni
Hi @elibroftw! i've fixed it by including: ``` ``` in `head` of your `public/index.html` file. Hope it helps!
> Using `@latest` helped resolve my issue (unresolved promise). > > This is the error I was getting before using `@latest` > > ``` > node:internal/process/promises:265 > ``` @kevinvangelder for...
any update on this? :) thanks for your pr!
same here, @onurkantar i've tried but after i got problems on imports Script, ScriptManager etc. Any adivice? 🙏 @RafikiTiki
Hi @RafikiTiki thanks a lot for answer, i'm trying but i'm not a webpack expert. The thing that I know is that the error is raised after this: dist/webpack/Compiler.js ```...
ok, now i'm going deep: investingating on `getWebpackEnvOptions`, where the crash is located and function never be called
@RafikiTiki i was able to make it run by this really poor workaround: in `webpack.config.mjs` setting dirname=context in `dist/webpack/webpackWorker.js`: ``` async function main(_cliOptions) { const cliOptions = { ..._cliOptions, config:{...
@RafikiTiki I don't know how to make a pull request that doesn't break anything or where to change to integrate the fix into source, but I remain at your complete...
also for me, i think that this prj is not mainteined anymore... so sad