Dependency & CI fixes

[kremalicious]

• fixes Update lockfileVersion and use npm v >7 #1025
• fixes Fix builds #1026

[netlify]

✅ Deploy Preview for docs-oceanprotocol ready!

Name	Link
🔨 Latest commit	1d1aa40
🔍 Latest deploy log	https://app.netlify.com/sites/docs-oceanprotocol/deploys/62b1b5d377999b2c4606fad9
😎 Deploy Preview	https://deploy-preview-1030--docs-oceanprotocol.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[qlty-cloud-legacy]

Code Climate has analyzed commit 1d1aa40 and detected 0 issues on this pull request.

View more on Code Climate.

[kremalicious]

because we can't deploy anything right now. Do we want to stop updating any content of the docs until some magical migration in the future?

But yes, generally agree and this repo is a perfect example of what happens when maintenance of the underlying dependencies stops. We are now multiple major versions behind of most dependencies and they simply stop working in combination with other dependencies. Maintaining the docs in the future can only mean maintaining the tech too.

[kremalicious]

Had to explicitly set --legacy-peer-deps via NPM_FLAGS env vars in Netlify https://docs.netlify.com/configure-builds/manage-dependencies/#npm

All dependencies are multiple major versions behind, so everything in here is legacy and no general npm i will work

[kremalicious]

great, now npm start locally doesn't work anymore because of some other dependency conflict. I hate this unmaintained repo, probably easier to abandon it and just copy the content/ folder.

Deployment is more important than local development so merging anyway

[alexcos20]

thanks

[jamiehewitt15]

probably easier to abandon it and just copy the content/ folder.

Yeah, good point. I'm happy to help with that if needed.

[jamiehewitt15]

I created a new issue to discuss starting again with the docs #1031