[Cloud] Re: Building Node.js project (and deploy script)

Sportzpikachu via Cloud (24.08.2024 12:09): How long does your build take locally? It might be timing out on toolforge. 4 seconds on 3,6GHz PC, but it has some large modules: WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 Ki

[Cloud] Re: Building Node.js project (and deploy script)

You might also look into , which builds your code (semi-) automatically, and hopefully with larger RAM limits (since it’s only for build, not for run, i.e. a fairly rare scenario, it can be more generous). See for how to specify the correct Node.js version. (Dis

[Cloud] Re: Building Node.js project (and deploy script)

By default there are fairly low ram limits on TF, you are probably hitting those and it’s getting killed. On Sat, Aug 24, 2024 at 7:03 AM Aoyan Sarkar wrote: > From personal experience, Webpack builds are very RAM intensive, can > easily consume a gigabyte+ of RAM if you’re not careful. It would

[Cloud] Re: Building Node.js project (and deploy script)

From personal experience, Webpack builds are very RAM intensive, can easily consume a gigabyte+ of RAM if you’re not careful. It would be best to build locally and upload the artifacts to Toolforge. —Aoyan Sarkar > On Aug 24, 2024, at 6:09 AM, Sportzpikachu via Cloud > wrote: > > How long d

[Cloud] Re: Building Node.js project (and deploy script)

How long does your build take locally? It might be timing out on toolforge. If you're simply hosting static files, it might be easier to build on Github CI and then just wget the built artifact into `$HOME/www/static` (

[Cloud] Building Node.js project (and deploy script)

Hi, Is it allowed to build a webpack app in Toolforge environment? I'm asking because I tried to build an Agular app (old ng) for Wiki Loves Monuments and failed. I did found this instructions: https://wikitech.wikimedia.org/wiki/Help:Toolforge/Node.js#Running_npm_with_webservice_shell And Nod