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

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

• I'd be willing to implement this feature
• This feature can already be implemented through a plugin

Describe the user story

I was looking into patch and how it works, but the docs didnt give much info. The CLI also didnt. I had to look around to get an idea of it. I thought it worked similar like patch-package. However, it works differently.

**Describe the solution you'

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?