WinDev
yarn
Our great sponsors
WinDev | yarn | |
---|---|---|
14 | 34 | |
429 | 41,324 | |
0.7% | 0.0% | |
0.0 | 0.0 | |
11 months ago | 27 days ago | |
JavaScript | ||
MIT License | GNU General Public License v3.0 or later |
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.
WinDev
-
Inexplicable lag when opening media folders, Windows reloads every file individually
Trying to research this a little more, I came across a post that certainly seems to mimic the issue.
-
Control Center on macOS is always re-rendering its SwiftUI causing 1% CPU load
> compressed memory
doesn't solve much and it's been available in all other OS for a long time.
many reported that compressed memory can negatively impact performances in certain scenarios
For example
https://github.com/microsoft/Windows-Dev-Performance/issues/...
- Thanks for everything, WinRAR: Windows is finally getting native RAR support
-
I condensed down 30 million JPGs to 2.6TB and it takes me 6 days to move them
You can see pretty easily if you ever try to delete a node_modules folder on Windows: https://github.com/microsoft/Windows-Dev-Performance/issues/17 There's some anectdotal evidence in there that FS performance is better in Linux even when Linux is emulated in WSL2 instead of native Windows.
-
This delay happens when I open any folder with videos in it. Is it normal behavior or should I change any settings? (Using Windows 11 22h2 latest official build).
issue on github
- Switching back to Windows showed me why Linux is more viable than ever
- Alternatives to CCleaner?
-
Announcing Windows 11 Insider Preview Build 22471 for the Dev Channel
Addressed an issue where when explorer.exe is launched from an elevated process was using a lower memory priority, impacting the performance of all processes launched after it (Issue #55).
-
“The entire 11 MB ZIP file was being read from disk a single byte at a time”
A bug has been filed about this on the WinDev repo, might help resolve it faster if it gets some upvotes: https://github.com/microsoft/Windows-Dev-Performance/issues/...
-
Notepad running next to gedit using the initial WSL GUI app support
There are performance issues with POSIX-first software on Windows. There is an open issue for the Windows team about it on Github. You can read more about it here. That's why WSL is needed.
yarn
- Configurar Solana en Linux
-
Set up your own LMQL environment.
instead. Please refer tothis issue for guidance. Following the instructions in this issue will ensure the correct installation of Yarn.
-
What is jQuery?
As an alternative, you can use the Yarn CLI command:
-
Lockfile merge conflicts, how to handle it correctly?
The PR for Auto detect and merge lockfile conflicts provides insight into the latest implementation in /src/lockfile/parse.js.
-
Yarn Install Broken
this this maybe https://github.com/yarnpkg/yarn/issues/8331
-
How I Built an Android Ecommerce App with Medusa
Yarn, but you can use npm or pnpm as alternatives to yarn if you prefer.
-
Benchmarks of JavaScript Package Managers
Yarn definitely shot themselves in the foot badly. PnP identified real problems & came up with a solution, but pnpm is doing a similar set of tricks but in a Node-ecosystem-compatible way, with next to no compatibility issues (versus package maintainers having to each individually support Yarn V2 PnP). Yarn V2 seemingly thought they could get the entire npm package world to switch to yarn, saw their growth & saw the thought-leaders & decided their winning was a fait-accompli.
And they didn't really execute very well... v2 landed, there was controversy, and there's been so little visible or exciting good news about it. It over-played Yarns so hand they renamed Yarn v2 as Berry, just to re-gather the troops & make a staging point forward. But it's still an incredibly hard pill to swallow, and the "yarn (berry) is great, the ecosystem needs to change" attitude seemingly isn't gaining any traction and it's hard to tell where Yarn could go.
In Yarn v3[1], they've introduced a modular "linker" system for how to install packages, that seemingly might get them able to experiment around/play around a little more & be less constrained than the hard-path they'd crusaded for.
One thing I will say for Yarn, that makes me unbelievably happy versus npm (announced during the V2[2] announcement):
> Yarn is first and foremost a Node API that can be used programmatically (via @yarnpkg/core)
Npm is the premier tool for open-source javascript, but it itself is one of the least open-source efforts on the planet. I finally started digging around the npm package and it's underlying cacache cache-structure, and it's just infinitely unpleasant to get started with. There's maybe like 3 articles on the whole planet that have any guidance for what npm is inside, how it works, what you can do with it, how you can hack it. Yarn identifying that the package manager itself is something that developers need access to is a huge win & I want to thank them forever for putting that on their bullet list of great Yarn things.
[1] https://dev.to/arcanis/yarn-3-0-performances-esbuild-better-...
[2] "Yarn's Future - v2 and beyond" https://github.com/yarnpkg/yarn/issues/6953
-
Using TypeScript 4.9 with Next.js 12
Unfortunately, as I found out, yarn's resolutions property has a long history of not playing well with optionalDependencies: anything placed into resolutions is treated as required and will abruptly fail to install if it is, for example, a platform-specific package appropriate for your deploy environment but not your dev environment or vice versa, as is the case here.
-
TypeScript all-in-one: Monorepo with its pains and gains
It was July 2021. I started with [email protected] since I’ve been using it for a long time. Yarn was fast, but soon I met several issues with Yarn Workspaces. E.g., not hoisting dependencies correctly, and tons of issues are tagged with “fixed in modern”, which redirects me to the v2 (berry).
-
Why aren't Node.js package managers interoperable?
Upgrading dependencies: Yarn 1's yarn upgradeonly upgrades direct dependencies of the current workspace. Yarn 2's up ignores the version ranges in your package.json and upgrades for all workspaces. npm's and pnpm'supdate respect your version ranges and upgrade indirect dependencies as well.
What are some alternatives?
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
berry - 📦🐈 Active development trunk for Yarn ⚒
dotnet - This repo is the official home of .NET on GitHub. It's a great starting point to find many .NET OSS projects from Microsoft and the community, including many that are part of the .NET Foundation.
pnpm - Fast, disk space efficient package manager
openjdk - Microsoft Build of OpenJDK
Bower - A package manager for the web
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
npm
ProjectReunion - The Windows App SDK empowers all Windows desktop apps with modern Windows UI, APIs, and platform features, including back-compat support, shipped via NuGet.
yarn-deduplicate - Deduplication tool for yarn.lock files
biden-approval-ratings - An open source polling average for President Joe Biden's approval ratings done in Python.
setup-node - Set up your GitHub Actions workflow with a specific version of node.js