You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Once changed to / for gh-pages deploy target check again what assets get published for noise, or consider some (other? like /build as when dev?) output folder and only publish its contents to gh-pages root? — needed anyways for local webpack output, tbd examine 3rdparty actions for webpack workflow inspiration deploying github-pages env instead of committing gh-pages to branch…)
General build OQs:
works only with node 14 (EOL), fails on 16; should be updated to current LTS which is 20!
(GH actions only support node16 starting this summer, so at least 16 compatibility must be resolved to be able to build webpack output to gh-pages using actions…)
webpack 4.46>4.47 update should support node18+…
has some rather old deps, worth trying to bring more up to date?
@gene1wood began updating to webpack5: gene1wood@4f8500d with all the deps, let's see if that resolves all the LTS compatibility & audit findings…
The text was updated successfully, but these errors were encountered:
Easy with current /docs output, see Netlify PoC:
(Once changed to / for gh-pages deploy target check again what assets get published for noise, or consider some (other? like /build as when dev?) output folder and only publish its contents to gh-pages root? — needed anyways for local webpack output, tbd examine 3rdparty actions for webpack workflow inspiration deploying github-pages env instead of committing gh-pages to branch…)
General build OQs:
The text was updated successfully, but these errors were encountered: