yarn
Here are 2,603 public repositories matching this topic...
-
Updated
Jul 29, 2020 - JavaScript
-
Updated
Jul 30, 2020 - JavaScript
This is the first try using GatsbyJS as website:
Goals
- To have a more flexible website
- Be able to add new pages based on different sources (GitHub, Markdown, etc etc)
- Improve SEO experience
- Custom versioning (nice to have): We don't want to build versioning for each change, versioning should be immutable. Eg: If we are on
v5.0.0and we release a patch version, thev5.0.0wi
Current Behavior
To export umd module, I would like to include all modules into the bundle, so I config the rollup
if (config.output.format === 'umd') {
delete config.external;
}
but when building, it crashes:
(babel plugin) SyntaxError: /Users/bytedance/workspace/ee_web_apps-menu/node_modules/lodash-es/isBuffer.js: 'import' and 'export' may only appe
-
Updated
Aug 17, 2020 - JavaScript
I'm not sure if this is the right approach and maybe I've not understood this new part of the pipeline, yet, but:
Suppose, the major part of the app code lives inside a rails engine including all javascripts. And there are several main apps using that engine. The main apps only contain some layout changes and some minor patches.
Therefore, in order to integrate the webpacker gem into this se
-
Updated
Aug 14, 2020
-
Updated
Aug 19, 2020 - TypeScript
-
Updated
Jul 15, 2020 - JavaScript
Describe the user story
Currently when running yarn upgrade-interactive it lists all installed packages and lazily displays new packages. When working on a project that has many dependencies (>20) this can get out of hand easily where you're scrolling for a while until you've "found" the first package with a new available version.
Describe the solution you'd like
I suggest
-
Updated
Aug 17, 2020 - TypeScript
-
Updated
Jul 16, 2020 - JavaScript
-
Updated
May 20, 2020 - Java
-
Updated
Mar 15, 2020 - PHP
-
Updated
Jul 7, 2020 - JavaScript
-
Updated
Oct 8, 2018 - TypeScript
-
Updated
Aug 17, 2020 - JavaScript
-
Updated
Nov 28, 2018 - JavaScript
-
Updated
Jun 28, 2020 - TypeScript
Improve this page
Add a description, image, and links to the yarn topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the yarn topic, visit your repo's landing page and select "manage topics."
Do you want to request a feature or report a bug?
feature request
What is the current behavior?
Currently
yarn whywon't indicate any package info in the resolutions fieldIf the current behavior is a bug, please provide the steps to reproduce.
"pkg": "^1.0.0"resolutionsfield in package.json,pkg: "1.0.0"