git-lfs
Babel (Formerly 6to5)
Our great sponsors
git-lfs | Babel (Formerly 6to5) | |
---|---|---|
158 | 57 | |
12,346 | 42,844 | |
1.2% | 0.2% | |
9.1 | 9.8 | |
7 days ago | 6 days ago | |
Go | TypeScript | |
GNU General Public License v3.0 or later | MIT 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-lfs
- Twenty Years Is Nothing
-
Aho â a Git implementation in Awk
It doesn't, since Git's data model has to be changed to content-defined chunks to solve the issue.
You should look at git-lfs[1] instead.
-
Launch HN: Diversion (YC S22) â Cloud-Native Git Alternative
Congrats on the HN launch. How does this improve or expand or blow git-lfs[1] out of the water because if I needed large blob file support it's what I would use instead. It offers pointers to the big files to the hosted git instead of pushing around the binaries itself -- though I am speculating since I've not used it myself just read about it online.
-
Ask HN: Can we do better than Git for version control?
fine with layers: e.g., large binary files via git-lfs (https://git-lfs.com) and merge conflicts in non-textual files by custom merge resolvers like Unityâs (https://flashg.github.io/GitMerge-for-Unity/).
Perhaps in the future, almost everyone will keep using Git at the core, but have so many layers to make it more intuitive and provide better merges, that what theyâre using barely resembles Git at all. This flexibility and the fact that nearly everything is designed for Git and integrates with Git, are why I doubt itâs ever going away.
Some alternatives for thought:
- pijul (https://pijul.org), a completely different VCS which allegedly has better merges/rebases. In beta, but I rarely hear about it nowadays and have heard more bad than good. I donât think we can implement this alternate rebases in Git, but maybe we donât need to; even after reading the website, I donât understand why pijulâs merges are better, and in particular I canât think of a concrete example nor does pijul provide one.
- Unison (https://www.unison-lang.org). This isnât a VCS, but a language with a radical approach to code representation: instead of code being text stored in files, code is ASTs referenced by hash and stored in essentially a database. Among other advantages, the main one is that you can rename symbols and they will automatically propagate to dependencies, because the symbols are referenced by their hash instead of their name. I believe this automatic renaming will be common in the future, whether itâs implemented by a layer on top of Git or alternate code representation like Unison (to be clear, Unisonâs codebases are designed to work with Git, and the Unison project itself is stored in Git repos).
- SVN, the other widespread VCS. Google or ask ChatGPT âGit vs SVNâ and youâll get answers like this (https://www.linode.com/docs/guides/svn-vs-git/, https://stackoverflow.com/a/875). Basically, SVN is easier to understand and handles large files better, Git is decentralized and more popular. But what about the differences which canât be resolved by layers, like lazygit for intuition and git-lfs for large files? It seems to me like even companies with centralized private repositories use Git, meaning Git will probably win in the long term, but I donât work at those companies so I donât really know.
- Mercurial and Fossil, the other widespread VCSs. It seems these are more similar to Git and the main differences are in the low-level implementation (https://stackoverflow.com/a/892688, https://fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki#....). It actually seems like most people prefer Mercurial and Fossil over Git and would use them if they had the same popularity, or at least if they had Gitâs popularity and Git had Mercury or Fossilâs. But again, these VCSs are so similar that with layers, you can probably create a Git experience which has their advantages and almost copies their UI.
- We Put Half a Million Files in One Git Repository, Here's What We Learned (2022)
-
Show HN: Gogit â Just enough Git (in Go) to push itself to GitHub
I donât know what that is, but their docs very prominently and strongly say this:
> However, we do not maintain a stable Go language API or ABI, as Git LFS is intended to be used solely as a compiled binary utility. Please do not import the git-lfs module into other Go code and do not rely on it as a source code dependency.
> I donât know what that is
its a standard output from `go doc`, rendered as HTML. if you dont recognize that, then you aren't really in a position to be commenting on the topic. nothing is stopping anyone from pinning to a tag:
https://github.com/git-lfs/git-lfs/tags
or even a commit and relying of a specific version of the software. yes upgrades might be painful but a module IS available.
-
Unable to push because of large file deleted in the past
# git push origin feature-branch /usr/bin/gh auth git-credential get: 1: /usr/bin/gh auth git-credential get: /usr/bin/gh: not found /usr/bin/gh auth git-credential store: 1: /usr/bin/gh auth git-credential store: /usr/bin/gh: not found Enumerating objects: 9228, done. Counting objects: 100% (7495/7495), done. Delta compression using up to 8 threads Compressing objects: 100% (2090/2090), done. Writing objects: 100% (6033/6033), 72.77 MiB | 7.39 MiB/s, done. Total 6033 (delta 4402), reused 5194 (delta 3616) remote: Resolving deltas: 100% (4402/4402), completed with 477 local objects. remote: error: Trace: c1c90b47a5483929dcdd8c974a6c7d0695e86f67f680d8b88b80ef1c1bce74a remote: error: See https://gh.io/lfs for more information. remote: error: File deployment_20200220.sql is 872.78 MB; this exceeds GitHub's file size limit of 100.00 MB remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com. To https://github.com/my-org/my-project.git ! [remote rejected] rest-logging -> rest-logging (pre-receive hook declined) error: failed to push some refs to 'https://github.com/my-org/my-project.git'
- What and Why, Git LFS?
-
Coding your own AI in 2023 with fastai
Before commit we need to install git-lfs first, because our model.pkl file is too big. Follow the link and the instructions to install it for your operating system. Now we are able to use git-lfs for our model.pkl:
Babel (Formerly 6to5)
-
Mastering Jest Configuration for React TypeScript Projects with Vite: A Step-by-Step Guide
node 'node_modules/.bin/jest' '/Users/satparkash/code/test-app/src/A pp.test.tsx' -t 'App' FAIL src/App.test.tsx â Test suite failed to run SyntaxError: /Users/satparkash/code/test-app/src/App.test.tsx: Support for the experimental syntax 'jsx' isn't currently enabled (6:12): 4 | describe('App', () => { 5 | it('should work as expected', () => { > 6 | render(); | ^ 7 | }); 8 | }); 9 | Add @babel/preset-react (https://github.com/babel/babel/tree/main/packages/babel-preset-react) to the 'presets' section of your Babel config to enable transformation. If you want to leave it as-is, add @babel/plugin-syntax-jsx (https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-jsx) to the 'plugins' section to enable parsing. Test Suites: 1 failed, 1 total Tests: 0 total Snapshots: 0 total Time: 0.278 s Ran all test suites matching /\/Users\/satparkash\/code\/test-app\/src\/App.test.tsx/i with tests matching "App".
- Open source public fund experiment - One and a half years update
-
I Reworked my Rate My GMU Professor (Google Extension)
Webpack (Babel) - https://babel.dev/
-
Babel is used by millions, so why are we running out of money? (2021)
I do appreciate your transparency, though I disagree with the sentiment that Iâm arguing from a position of bad faith.
Itâs a self-evident fact that the Babel team has not shown a moment of interest in lowering their role in the JavaScript ecosystem to anything short of kingmakers. Have a gander at their GitHub README and what do we see?[1]
- âBabel is a compiler for writing next generation JavaScript.â Indefinitely.
- Over a dozen sponsor logos. An embarrassment of riches.
- A literal audio recording of a song in praise of the project.
The Babel team has a well documented history of their priorities[2], emphasizing the need for a modular approach that has no exit strategy[3]. At best, we have a case of accidental entrenchment and long term dependence on the Babel brewing as early as 2017![4]
Compare this infinite circus to the humble but popular Normalize.css, which has the express purpose to stop existing.[5]
If the Babel team wants to raise some money, they can start by putting a plan together that would codify an exit strategy. Itâs certainly more noble than their current plan of barnacling on to every NPM packageâŚ
- [1] https://github.com/babel/babel
- [2] https://github.com/babel/notes
- [3] https://github.com/babel/notes/blob/master/2016/2016-07/july...
- [4] https://github.com/babel/notes/blob/master/2017/2017-04/apri...
-
Reveddit does not work
The problem was I had used some new code, Javascript's replaceAll(), that is unsupported by older browsers. And, the setup I have to automatically fix such issues (called babel) is out of date. So, while this problem appears to be resolved there, I hadn't updated that in awhile.
-
The Complete Guide for Setting Up React App from Scratch (feat. TypeScript)
babel-loader(v9.1.0): allows transpiling JavaScript files using Babel and webpack.
-
Upgrade your Lerna Workspace - Make it Fast and Modern!
created 6 years ago to solve the specific problem of managing the Babel repo packages
- âIgnore the f'ing haters â And other lessons learned from creating a popular
-
React project structure for scale: decomposition, layers and hierarchy
There are quite a few public repositories of well-known projects that use the multi-packages monorepo approach: Babel, React, Jest to name a few.
-
NPM Vulnerability Discussion on Twitter
The reason it doesn't get called out is because the philosophy of "thousands of small packages" has spread far and wide. [1]
For every person calling it out like we're doing here, there are ten others praising maintainers able to whip ten semi-useless packages per week.
It's not just random maintainers making small packages. The core infrastructure of Javascript is in it. Babel is made of hundreds of packages, which all live on the same repository (because of course the maintainers don't want the hassle of maintaining multiple things). Some of those packages don't even have anything of importance in it, just metadata, a couple flags and some boilerplate [2]. The package is just a way of organizing code. Webpack, ESLint and others aren't exactly better.
The reason people do it is because other popular people have been doing it for a long time, and nobody calls them out on it.
[1] https://blog.sindresorhus.com/small-focused-modules-9238d977...
[1] https://github.com/babel/babel/blob/main/packages/babel-plug...
What are some alternatives?
Traceur compiler - Traceur is a JavaScript.next-to-JavaScript-of-today compiler
onedrive - OneDrive Client for Linux
Live Server - A simple development http server with live reload capability.
git-fat - Simple way to handle fat files without committing them to git, supports synchronization using rsync
Gitea - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
ESLint - Find and fix problems in your JavaScript code.
git - A fork of Git containing Windows-specific patches.
Lebab - Turn your ES5 code into readable ES6. Lebab does the opposite of what Babel does.
nixpkgs - Nix Packages collection & NixOS
scalar - Scalar: A set of tools and extensions for Git to allow very large monorepos to run on Git without a virtualization layer
dark-mode - Control the macOS dark mode from the command-line
Bazel - a fast, scalable, multi-language and extensible build system