devtools-frontend

The GitHub mirror of the Chrome DevTools repo has the node_modules folder here: https://github.com/ChromeDevTools/devtools-frontend/blob/mai... But there is nuance (there always is...), the README file in node_modules is here: https://github.com/ChromeDevTools/devtools-frontend/blob/mai... - and it makes it clear the only NPM dependencies used by the build-system or infrastructure is meant to be checked-in. Other NPM packages should not. ---------- In conclusion: the linked blog-article is clickbait that misrepresents how the Chrome team manages their dependencies.

Chrome DevTools has their own separate repo * https://developer.chrome.com/docs/devtools/ * It's mirrored on GitHub: https://github.com/ChromeDevTools/devtools-frontend * And look, THAR SHE BLOWS: https://github.com/ChromeDevTools/devtools-frontend/tree/mai...

2 known issues: - DevTools doesn't display the viewport. I'm not sure if this is due to a change in the latest Chrome to which I just updated (~90) or because I broke my serving of it by updating it. A workaround will be serving a static snapshot of the devtools front-end rather than just (simply, as I'm doing right now) pulling it out of Chrome's RDP endpoint each time. This may take some time to do. - DevTools doesn't seem to work on iOS (as I've tested it, Safari or Chrome). - There are many more issues, and a lot, but not all, of them are edge cases but they'll be fixed eventually. More bug reports, UI/UX tips and advice, and other feedback are very welcome! Unfortunately the whole app is not open source but some parts are open source, namely, the virtualized browser[0], and the devtools-front-end[1]. [0]: https://github.com/i5ik/View