Laravel Homestead vs Yarn

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Laravel Homestead
Laravel Homestead

186
173
+ 1
33
Yarn
Yarn

3.7K
2.5K
+ 1
116
Add tool

Laravel Homestead vs Yarn: What are the differences?

Developers describe Laravel Homestead as "The official Laravel local development environment (Vagrant box)". Laravel Homestead is an official, pre-packaged Vagrant "box" that provides you a wonderful development environment without requiring you to install PHP, HHVM, a web server, and any other server software on your local machine. Homestead runs on any Windows, Mac, or Linux system, and includes the Nginx web server, PHP 5.6, MySQL, Postgres, Redis, Memcached, and all of the other goodies you need to develop amazing Laravel applications. On the other hand, Yarn is detailed as "A new package manager for JavaScript". Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever.

Laravel Homestead belongs to "Virtual Machine" category of the tech stack, while Yarn can be primarily classified under "Front End Package Manager".

"Easy to setup" is the top reason why over 18 developers like Laravel Homestead, while over 74 developers mention "Incredibly fast" as the leading cause for choosing Yarn.

Laravel Homestead and Yarn are both open source tools. Yarn with 36.1K GitHub stars and 2.21K forks on GitHub appears to be more popular than Laravel Homestead with 3.11K GitHub stars and 1.32K GitHub forks.

StackShare, Docplanner, and BrightMachine are some of the popular companies that use Yarn, whereas Laravel Homestead is used by Balliza, Pitcherific, and Timekit. Yarn has a broader approval, being mentioned in 609 company stacks & 507 developers stacks; compared to Laravel Homestead, which is listed in 20 company stacks and 24 developer stacks.

What is Laravel Homestead?

Laravel Homestead is an official, pre-packaged Vagrant "box" that provides you a wonderful development environment without requiring you to install PHP, HHVM, a web server, and any other server software on your local machine. Homestead runs on any Windows, Mac, or Linux system, and includes the Nginx web server, PHP 5.6, MySQL, Postgres, Redis, Memcached, and all of the other goodies you need to develop amazing Laravel applications.

What is Yarn?

Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Laravel Homestead?
Why do developers choose Yarn?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use Laravel Homestead?
    What companies use Yarn?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Laravel Homestead?
    What tools integrate with Yarn?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Laravel Homestead and Yarn?
    Docker
    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere
    Laravel
    It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.
    XAMPP
    It consists mainly of the Apache HTTP Server, MariaDB database, and interpreters for scripts written in the PHP and Perl programming languages.
    HHVM (HipHop Virtual Machine)
    HHVM uses a just-in-time (JIT) compilation approach to achieve superior performance while maintaining the flexibility that PHP developers are accustomed to. To date, HHVM (and its predecessor HPHPc before it) has realized over a 9x increase in web request throughput and over a 5x reduction in memory consumption for Facebook compared with the PHP 5.2 engine + APC.
    Azure Virtual Machines
    You can create Linux and Windows virtual machines. It gives you the flexibility of virtualization for a wide range of computing solutions—development and testing, running applications, and extending your datacenter. It’s the freedom of open-source software configured the way you need it.
    See all alternatives
    Decisions about Laravel Homestead and Yarn
    Tim Abbott
    Tim Abbott
    Founder at Zulip · | 3 upvotes · 7.1K views
    atZulipZulip
    Node.js
    Node.js
    npm
    npm
    Yarn
    Yarn

    I have mixed feelings on the Yarn/npm/Node.js ecosystem. We use it for Zulip, because you basically have to in order to have a modern JavaScript toolchain. And I like that Yarn lets us pin dependency versions out of the box for predictability in our production releases; we have to do significant work for the Python version of this feature.

    But one also deals with broken third-party dependencies uploaded to npm way too often (even ignoring the malicious packages issues that have gotten a lot of press of late). And one mostly has to use nvm in order to pin a specific version of node itself in a maintainable way, and nvm is a mess.

    See more
    Russel Werner
    Russel Werner
    Lead Engineer at StackShare · | 5 upvotes · 6.3K views
    atStackShareStackShare
    npm
    npm
    Yarn
    Yarn

    We use Yarn because at the time we decided to adopt it, npm had some missing features and issues. We like the speed and determinism provided by Yarn. We could probably use npm at this point, but we have no real reason to switch from Yarn. If you have a convincing argument to switch from npm to Yarn please leave a comment on this decision!

    See more
    Johnny Bell
    Johnny Bell
    Senior Software Engineer at StackShare · | 17 upvotes · 71.4K views
    ESLint
    ESLint
    Prettier
    Prettier
    Babel
    Babel
    npm
    npm
    Yarn
    Yarn
    Node.js
    Node.js
    Webpack
    Webpack
    #ES5
    #ES6

    So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

    So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

    The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

    I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

    Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

    I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

    See more
    Yarn
    Yarn

    p.s.

    I am not sure about the performance of the latest version of npm, whether it is different from my understanding of it below. Because I use npm very rarely when I had the following knowledge.

    ------⏬

    I use Yarn because, first, yarn is the first tool to lock the version. Second, although npm also supports the lock version, when you use npm to lock the version, and then use package-lock.json on other systems, package-lock.json Will be modified. You understand what I mean, when you deploy projects based on Git...

    See more
    Mark Nelissen
    Mark Nelissen
    CTO at Gemsotec bvba · | 4 upvotes · 2.9K views
    Yarn
    Yarn
    TypeScript
    TypeScript
    React
    React
    npm
    npm

    I use npm because I also mainly use React and TypeScript. Since several typings (from DefinitelyTyped) depend on the React typings, Yarn tends to mess up which leads to duplicate libraries present (different versions of the same type definition), which hinders the Typescript compiler. Npm always resolves to a single version per transitive dependency. At least that's my experience with both.

    See more
    Jason Barry
    Jason Barry
    Cofounder at FeaturePeek · | 4 upvotes · 9K views
    atFeaturePeekFeaturePeek
    npm
    npm
    Yarn
    Yarn
    Babel
    Babel
    Sublime Text
    Sublime Text
    JavaScript
    JavaScript
    React
    React
    TypeScript
    TypeScript
    Flow (JS)
    Flow (JS)
    #Frontend

    I think our #Frontend stack is pretty standard – but we have taken some deviations from a typical modern stack:

    • Flow (JS) instead of TypeScript. Flow was an easy choice 2+ years ago, as both flow and React were (and still are) maintained by Facebook. Today, it seems that the JavaScript community has settled on TypeScript as the winner. For new projects, I'd choose TS, but I don't see the point in migrating an existing project from flowtype to TS, when the end result will be roughly the same. Sure, memory usage is a bit high, and every now and then I have to kill some zombie processes, but our text editors (Sublime Text), CI scripts, and Babel are already set up to take advantage of the type safety that flow offers. When/if the React team writes React itself in TS, then I'll take a closer look – until then, flow works for us.

    • Yarn instead of npm. When yarn debuted, we never looked back. Now npm has pretty much caught up with speed and lockfiles, but yarn gives me confidence that my dependency installs are deterministic. Really interested in the plug-n-play (PnP) feature that removes the need for a node_modules folder, but haven't implemented this yet.

    See more
    Yarn
    Yarn
    npm
    npm
    Node.js
    Node.js

    From a StackShare Community member: “I’m a freelance web developer (I mostly use Node.js) and for future projects I’m debating between npm or Yarn as my default package manager. I’m a minimalist so I hate installing software if I don’t need to- in this case that would be Yarn. For those who made the switch from npm to Yarn, what benefits have you noticed? For those who stuck with npm, are you happy you with it?"

    See more
    Interest over time
    Reviews of Laravel Homestead and Yarn
    No reviews found
    How developers use Laravel Homestead and Yarn
    Avatar of Mick Dekkers
    Mick Dekkers uses YarnYarn

    Yarn is a wonderful alternative to the built-in npm command-line interface. Dependency installation is crazy fast, because it caches every package and performs operations in parallel.

    Avatar of Volkan Özçelik
    Volkan Özçelik uses YarnYarn

    I prefer yarn instead of npm.

    Both npm and yarn work great.

    I don’t see any overwhelming reason to choose one over another.

    I just like yarn, that’s it.

    Avatar of Ambar
    Ambar uses YarnYarn

    We use it in every JS project. Blazing fast package manager for node.js. Easy to use in Docker containers

    Avatar of Coolfront Technologies
    Coolfront Technologies uses YarnYarn

    Used in Coolfront Mobile and "Charlie" (flat rate search engine) as packaging mechanism.

    Avatar of IVS
    IVS uses YarnYarn

    We tend to stick to npm, yarn is only a fancy alternative, not 10x better.

    How much does Laravel Homestead cost?
    How much does Yarn cost?
    Pricing unavailable
    Pricing unavailable