(https://yarnpkg.com/zh-Hans/)
Yarn is a package manager for your code. It allows you to use and share code with other developers from around the world. Yarn does this quickly, securely, and reliably so you don’t ever have to worry.
Yarn allows you to use other developers’ solutions to different problems, making it easier for you to develop your software. If you have problems, you can report issues or contribute back, and when the problem is fixed, you can use Yarn to keep it all up to date.
Code is shared through something called a package (sometimes referred to as a module). A package contains all the code being shared as well as a
from https://yarnpkg.com/en/docs/getting-started
------------
Before you start using Yarn, you'll first need to install it on your system. There is a growing number of different ways to install Yarn:
On Ubuntu 14.04 and Debian Stable, you will also need to configure the NodeSource repository
to get a new enough version of Node.js (Debian Testing and Ubuntu 16.04
come packaged with a sufficient version of Node.js, so this step is not
required in those environments)
Then you can simply:
If you do not already have Node.js installed, you should also configure
the NodeSource repository:
Then you can simply:
If you use an AUR Helper such as yaourt you can simply run:
Add
Test that Yarn is installed by running:
See how to install nightly builds
from https://yarnpkg.com/en/docs/install#linux-tab
---------------------
I wrote a piece to sbot that said 'imagine if
The reason I decided to try to live without
We will all be fucked, that's what. Because after 4 days of trying to live without
When you're working with distributed technologies, the most important thing to keep in mind is not relying on a centralized authority. Instead, the goal is to be distributed. We want everyone to be able to install our software whether or not
Now, I know
Here's what I mean when I say distributed:
Distributed technologies are not reliant on one single server. Instead, they share data between many nodes making it available to everyone. In the specific case of ssb we are replicating the data of our friends, and our friends friends on our computers so that it is available when our crappy wifi is down, and in the event of a nuclear war -- even though that'll (probably) never happen.
Ok, so how are we going to live without
This is the problem I faced 4 months ago when I decided to try to live without
Being a fairly terrible coder, I had no idea how to write this tool myself. Now, everything would be alright if
Now many people said 'oh, just use an
So I failed. I gave up. I went back to using
But it turns out that another organization has this same problem too. And it's not the kind of organization that you'd expect to want to encourage everyone to distributed everything... Facebook.
I know, I hate it. It's horrible. But you know how tech companies, before they go under, have guys at them with actual skills who want to get jobs after the bust? Well, a few of those guys are working on a cool project. It's called Yarn. It's all sweet and shit. There's a cat silo. The goal of their project is not to kill
So it turns out that Facebook and distributed social have the same problem. We don't want to depend on centralized technologies.
However our usecase is very different. Facebook wants to keep everything secret, and we want to keep everything available to everyone.
Yarn is pretty cool. It's a tool very similar to
In our case, we want to install our packages from a distributed social network. The easiest way to do this right now is commit our dependencies using
To do this, reading this article on creating an offline mirror with yarn is very interesting.
To create an offline mirror of your dependencies, all you gotta do is create a
Here's the one for minbay.
Next, type
Once the
Instead of the install flow looking this way:
Instead of installing
The other cool thing about Yarn is if you're not on ssb, you can fall back to a traditional mirror which will install your dependencies from a remote.
from http://evbogue.com/distributednodepackages/
Yarn is a package manager for your code. It allows you to use and share code with other developers from around the world. Yarn does this quickly, securely, and reliably so you don’t ever have to worry.
Yarn allows you to use other developers’ solutions to different problems, making it easier for you to develop your software. If you have problems, you can report issues or contribute back, and when the problem is fixed, you can use Yarn to keep it all up to date.
Code is shared through something called a package (sometimes referred to as a module). A package contains all the code being shared as well as a
package.json file which describes the package.from https://yarnpkg.com/en/docs/getting-started
------------
Before you start using Yarn, you'll first need to install it on your system. There is a growing number of different ways to install Yarn:
Debian/Ubuntu Linux
On Debian or Ubuntu Linux, you can install Yarn via our Debian package repository. You will first need to configure the repository:curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
Then you can simply:
sudo apt-get update && sudo apt-get install yarn
CentOS / Fedora / RHEL
On CentOS, Fedora and RHEL, you can install Yarn via our RPM package repository.sudo wget https://dl.yarnpkg.com/rpm/yarn.repo -O /etc/yum.repos.d/yarn.repo
curl --silent --location https://rpm.nodesource.com/setup_6.x | bash -
sudo yum install yarn
Arch Linux
On Arch Linux yarn can be installed through the AUR.If you use an AUR Helper such as yaourt you can simply run:
yaourt -S yarn
Solus
On Solus, you can install yarn via the Solus repository.sudo eopkg install yarn
Path Setup
You will need to set up thePATH environment variable in your terminal to have access to Yarn’s binaries globally.Add
export PATH="$PATH:`yarn global bin`" to your profile (this may be in your .profile, .bashrc, .zshrc, etc.)yarn --versionNightly Builds
Nightly builds are the latest and greatest versions of Yarn, built using the very latest Yarn source code. Nightly builds are useful to try new features or test bug fixes that have not yet been released as part of a stable release. However, these builds are not guaranteed to be stable and may have bugs.See how to install nightly builds
Problems? If you are unable to install Yarn with any of these installers, please search through GitHub for an existing issue or open a new one.
Search for an existing issue · Open a new issue
from https://yarnpkg.com/en/docs/install#linux-tab
---------------------
How to live without npm (using yarn for distributed package management tool)
Four months ago I got it into my head that I was going to live withnpm for month. I lasted for 4 days, and managed to piss off npm's lawyer. Although I'm sure he'll say I didn't get to him. It's cool, we down now ke.I wrote a piece to sbot that said 'imagine if
npm went down tomorrow' and that started the conversation. The thread is available on ssb-viewer if you want to read it.The reason I decided to try to live without
npm was
simple. I'm working on a distributed social network, built with Node.
We've got a distributed version of FB. We've got a distributed version
of Twitter. We've got a distributed version of Github. But we're relying
on npm to install our packages. What if npm goes away? Or doesn't like me anymore? What will we or I do?We will all be fucked, that's what. Because after 4 days of trying to live without
npm
I was completely unable to install any Node software. I had to cheat
more times than I'm willing to admit to get even the most basic of
upgrades going. When you're working with distributed technologies, the most important thing to keep in mind is not relying on a centralized authority. Instead, the goal is to be distributed. We want everyone to be able to install our software whether or not
npm is around in a year or five. Or whether or not npm loves us. Now, I know
npm is doing their best. They've put in a
lot of hours. They've been a pivotal part of the Node world for years.
However, the pivotal part is the problem when we're trying to create
distributed technologies. Here's what I mean when I say distributed:
Distributed technologies are not reliant on one single server. Instead, they share data between many nodes making it available to everyone. In the specific case of ssb we are replicating the data of our friends, and our friends friends on our computers so that it is available when our crappy wifi is down, and in the event of a nuclear war -- even though that'll (probably) never happen.
Ok, so how are we going to live without
npm?This is the problem I faced 4 months ago when I decided to try to live without
npm.
My first thought was "I'll just clone the individual git repos down
from wherever and build them" but it turns out that every Node module
has dependencies of dependencies of dependencies, and thus it devolves
into this recursive problem of needing a tool to handle your install for
you. It's not dependency hell, it's only dependency purgatory because
you'll be installing your dependencies until you're old and frail. Being a fairly terrible coder, I had no idea how to write this tool myself. Now, everything would be alright if
npm would cache your dependencies in your project folder and install from there. But it turns out that npm always wants to phone home before installing. This makes you reliant on a centralized authority. Now many people said 'oh, just use an
npm mirror.' But that's also remote (so it won't work when you're offline), and I also discovered that all of the npm mirrors are down! Which makes it difficult to use them. While npm is nice enough to let you mirror all of the data they host, the trouble is that you have to mirror all
of their data -- which according to their website is over 350,000
modules. I don't want host all that data. I just want to host the data
to install a few distributed applications.So I failed. I gave up. I went back to using
npm on day 5, because how the hell was I going to solve this problem?But it turns out that another organization has this same problem too. And it's not the kind of organization that you'd expect to want to encourage everyone to distributed everything... Facebook.
I know, I hate it. It's horrible. But you know how tech companies, before they go under, have guys at them with actual skills who want to get jobs after the bust? Well, a few of those guys are working on a cool project. It's called Yarn. It's all sweet and shit. There's a cat silo. The goal of their project is not to kill
npm, it's just to solve their problem -- which is they are not allowed to use npm
because they are using packages that they don't want other people to
see. You know, all of those packages with human manipulation algorithms
built into them. Which is to say the interface for all of those old
ladies sitting in a back room hitting up/down on your Facemash posts.So it turns out that Facebook and distributed social have the same problem. We don't want to depend on centralized technologies.
However our usecase is very different. Facebook wants to keep everything secret, and we want to keep everything available to everyone.
Yarn is pretty cool. It's a tool very similar to
npm.
But instead of relying on a centralized authority, you can instead tell
it to install your node dependencies from another source. Yarn also
de-dupes packages faster than npm and uses checksums to guarantee file integrity -- so no one can slip malicious code into your dependencies. In our case, we want to install our packages from a distributed social network. The easiest way to do this right now is commit our dependencies using
git-ssb, clone them down, and install them using yarn. To do this, reading this article on creating an offline mirror with yarn is very interesting.
To create an offline mirror of your dependencies, all you gotta do is create a
.yarnrc file that says you want to save tarballs of your dependencies to your project folder.Here's the one for minbay.
# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
# yarn lockfile v1
yarn-offline-mirror "./ssb-pkgs"
yarn config set yarn-offline-mirror ./ssb-pkgs, and then moved the generated .yarnrc file into my project folder.Next, type
yarn, which will download all of your dependencies from npm or the yarn mirror, save them to your node_modules folder in a familiar fashion, and generate a yarn.lock file which tells yarn that you've done so. Once the
yarn install is over, you'll see a folder called ssb-pkgs which contains all of the node_modules in tarball form. You can check this into a git repo, push them to git-ssb and they will be available over the distributed social network.Instead of the install flow looking this way:
git clone git://project
cd project
npm install
npm start
git clone ssb://project project
cd project
git clone ssb://project-dependencies ssb-pkgs
yarn
yarn start
package.json install script. Instead of installing
npm, you need to install yarn and git-ssb -- and make sure that you're peered into the network.The other cool thing about Yarn is if you're not on ssb, you can fall back to a traditional mirror which will install your dependencies from a remote.
What now?
Now that we're no longer dependent onnpm, we can live
free on the Internet knowing that no centralized authority can ever run
out of startup funding and leave us hanging. Hurray!from http://evbogue.com/distributednodepackages/
