git-archive-all
devtools-frontend
| git-archive-all | devtools-frontend | |
|---|---|---|
| 2 | 7 | |
| 9 | 2,994 | |
| - | 1.3% | |
| 0.0 | 10.0 | |
| over 1 year ago | 3 days ago | |
| Shell | TypeScript | |
| MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
git-archive-all
-
Git archive checksums may change
- you have submodules (to which `git archive` is completely blind).
Note that `git-archive-all`[1] can help as long as your submodules don't do things like `[attr]custom-attr` in their `.gitattributes` as it is only allowed in the top-level `.gitattributes` file and cannot be added to the tree otherwise.
[1]https://github.com/roehling/git-archive-all
-
Why you should check-in your node dependencies
Thanks for sharing!
Depending on the context, if you don't want this in git history, and want to handle git submodules, there's also git-archive-all https://github.com/roehling/git-archive-all (if you like shell scripts, it is using bats for testing - it was the first time I heard of it)
devtools-frontend
-
Curl 8.0.1 because I jinked it
You can paste that curl command into https://curlconverter.com/wget/ to turn it into a Wget command.
> The reason there isn't a "Copy as wget" option, I think, is the level of control that curl allows so the request can be tailored to exactly mimic the browser.
This is not true. You can read the code that generates the curl command and it's pretty straightforward:
https://github.com/ChromeDevTools/devtools-frontend/blob/c9a...
The arguments it uses are --url, --data-raw, -X/--request, -H/--header, --compressed and --insecure, all of which Wget has an analog of. I think the reason is that they don't care to do it and/or they don't want to make that dropdown menu 30 entries long.
- Architecture and guiding principles of Chrome DevTools
-
Why you should check-in your node dependencies
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.
While you are correct about Google's monorepository, the author works on Chrome DevTools. That repository is open-source and standalone: https://github.com/ChromeDevTools/devtools-frontend
-
Debugging tools, branching strategies and many more resources
What's new in DevTools (Chrome 95).
-
Show HN: Run puppeteer scripts from the Browser, open DevTools on remote pages
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/ViewFinderJS
[1]: https://github.com/ChromeDevTools/devtools-frontend
What are some alternatives?
go-offline-maven-plugin - Maven Plugin used to download all Dependencies and Plugins required in a Maven build, so the build can be run without an internet connection afterwards.
remotedebug-ios-webkit-adapter - Debug Safari and WebViews on iOS from tools like VS Code and Chrome DevTools
aws-sdk-cpp - AWS SDK for C++
ViewFinderJS - :camera: ViewFinder - Remote isolated browser API for security, automation visibility and interactivity. RBI. CBII. Remote browser isolation, embeddable BrowserView, secure chrome-as-a-service. Managed, variable bandwidth and co-browsing options available in Pro versions. Like S2, WebGap, Bromium, Authentic8, Menlo Security and Broadcom, but free and open-source. Integrated secure document viewing with CDR from https://github.com/dosyago/p2%2e [Moved to: https://github.com/i5ik/ViewFinder]
SIG-rules-authors - Governance and admin for the rules authors Special Interest Group
cli - the package manager for JavaScript
picosnitch - Monitor Network Traffic Per Executable, Beautifully Visualized
depclean - DepClean automatically detects and removes unused dependencies in Maven projects (https://dx.doi.org/10.1007/s10664-020-09914-8)
github - Just a place to track issues and feature requests that I have for github
node-http2 - An HTTP/2 client and server implementation for node.js
jQuery-File-Upload - File Upload widget with multiple file selection, drag&drop support, progress bar, validation and preview images, audio and video for jQuery. Supports cross-domain, chunked and resumable file uploads. Works with any server-side platform (Google App Engine, PHP, Python, Ruby on Rails, Java, etc.) that supports standard HTML form file uploads.