Yarn

Do you want to request a feature or report a bug?
feature request

What is the current behavior?
Currently yarn why won't indicate any package info in the resolutions field

If the current behavior is a bug, please provide the steps to reproduce.

1. install a package with any version, e.g "pkg": "^1.0.0"
2. add resolutions field in package.json, pkg: "1.0.0"
3. upd

Describe the bug

I've built the verdaccio/verdaccio:local local image (Windows 10 latest, Docker Desktop) but cannot build the v4/5 reverse_proxy docker-examples.

To Reproduce

1. cd verdaccio && pnpm docker

2. cd verdaccio\docker-examples\v4\reverse_proxy\nginx\relative_path\ OR
   cd verdaccio\docker-examples\v5\reverse_proxy\nginx_relative\

3. docker-compose up

Current Behavior

UMD build doesn't support code-splitting and dynamic imports (rollup/rollup#3490, rollup/rollup#3491) due to Rollup current limitations, and tsdx cli don't accept the format option amd when creating build config

Suggested Solution

Consider support AMD module format, o

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

Self-service

• I'd be willing to implement a fix

Describe the bug

I'm using the ESLint extension in VSCode. Unfortunately it doesn't work with Plug'n'Play - according to the docs it should work if I understand correctly?

I've been looking at issues both here and in the ESLint extension repro but I haven't found anyone with this exact error it seems. I'm not sure if the issue belo

Describe the Feature

I would love to see the ability to pass in an xcconfig file to run-ios so that configs can be used to customize the build process with xcodebuild. This is a very important feature for whitelabeled applications that use xcconfig, scheme and configuration for different versions of an app. I was able to make a 2 line change to pass in the xcconfig locally and it worked with

In packages/components-typescript/package.json the fields main and main:src: refer to files that do not exist:

  "main": "src/index.tsx",
  "main:src": "src/index.tsx",

The index.tsx file is located in packages/components-typescript/index.tsx

Are these two fields redundant?