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

Type of issue: (feature suggestion, bug?)

Suggestion

Chapter:

no-chapter

Why use .jsx instead of .js? It's not a best practice: facebook/create-react-app#87 (comment)

Current Behavior

For every new project I start with TSDX, one of my first steps is to add stubs for static assets and stylesheets - as detailed on the Jest docs.

Desired Behavior

Add Jest file stubs in to the TSDX setup.

Suggested Solution

Following the Jest docs

// package.json
{
  "jest": {
    "m

We need to add tests for source/util.js, source/version.js, source/git-util.js and source/npm/util.js.

There is a $60.00 open bounty on this issue. Add mo

Is there any documentation on how to use less-loader with webpacker? I just spent the last four hours trying to figure out why my application was throwing a this[MODULE_NAME] is not a function because of a dependency upgrade, and found out that it was because in my loader I was using MiniCssExtractPlugin.loader, but webpacker was using its own internal version of MiniCssExtractPlugin. I wo

The features section in the docs states that nodemon is available in the project, when it's clearly not. It's not added as a dependency or as a command in the project. Maybe remove this from the docs or actually add nodemon?

• I'd be willing to implement a fix

Describe the bug

I'm working in a mono repo with yarn workspaces, and have noticed that yarn constraints does not always report all the errors that exist. I've tracked this down to be due to the default tau-prolog resolution step limit being used (1000), which wasn't enough in my case. (see http://tau-prolog.org/manual/a-simple-tutorial#sessions)

In the xlearning job web UI, the metrics graph can not be seen for these is no js for it.

I've noticed there are a lot of unused imports, bad syntax (doesn't follow style guide, isn't consistent) across the entire project. I could sweep up some junk for this project. Let me know your thoughts

This thing works, but reading the Yarn documentation seems to suggest it shouldn't be necessary. I've tracked a few issues in the Yarn repo that suggest potential root causes, but I'm sure the authors of this package would be in a better position to explain it 😄

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?

In the Quick usage guide Option 2, speak to use this command:

curl -L https://github.com/ambientum/cli/releases/download/v0.1.1/amb-`uname -s` -o /usr/local/bin/amb

but is the v before the release number gives an invalid url, the correct url is:

curl -L https://github.com/ambientum/cli/releases/download/0.1.1/amb-`uname -s` -o /usr/local/bin/amb