bug

So I have been trying to install this package redux-immutable-state-invariant with yarn.
I am using yarn add redux-immutable-state-invariant --dev. So, it correctly installs it in the dev dependencies but the issue is that when I import it in the file it gives me an error that says it can't resolve the path for the package.

So, looking into the issue myself I figured out that I am getting two different builds when I install it with yarn and with npm directly.

Also, be noted that when I install it with npm it works fine and doesn't give me a path issue. I am attaching screenshots for both directories in the node_modules package after installation.

With Yarn
See, no dist directory

With npm

yarn add redux-immutable-state-invariant --dev😕

BTW, please try to follow the issue template. It will make life easier for everyone.

Please mention your node.js, yarn and operating system version.

Ah, sorry about the issue template. I'll be surely strict about that in future.

I am still having this issue though.

node.js version: 6.9.1
OS: ubuntu 16
yarn: 0.16.1

Did you try this out on OSX? Because it works fine there for me as well.

@laumair yeah, I tried in macOS.

@torifat Hmmm. Not sure what the issue is then.

I just tried in Ubuntu 16.04. And, it's working as expected.

Can you yarn cache clean and try again?

@torifat after cleaning cache it works smooth. Thanks for testing it on your end as well and clearing out the issue. 👍

Do you want to request a feature or report a bug?
I think this is not really a bug, but just a wierd decision. So I request a feature.

What is the current behavior?
yarn install installs devDependencies of dependencies in my package.json
yarn install --prod avoids this, but it also doesn't install devDependencies in my package.json

What is the expected behavior?
I am definitely not developing the installed dependencies, but I want my own devDependencies to be installed. So I think this way is more convenient (in my opinion)

• yarn install should install OWN devDependencies but not devDependencies of dependencies.
• yarn install --prod should not install both own devDependencies and devDependencies of dependencies.
• yarn install --some-option acts similar to yarn install but including devDependencies of dependencies (for somebody with their own edge cases).

Please mention your node.js, yarn and operating system version.
Node v10.11.0
Yarn v1.10.1
Windows 10 Pro

yarn install should install OWN devDependencies but not devDependencies of dependencies.

That is how it works.

So my direct devDep left-pad is installed, my dependency's dependency is-online > got is installed, and my dependency's devDep is-online > ava is not installed.

If this isn't how it is working for you, I would run the yarn why command and see if something else happens to be depending on that package and causing it to be installed. Or if you can post a package.json that reproduces the issue I'd be happy to take a deeper look.

I created a repository for demonstration purpose:
https://github.com/hirikarate/issue-yarn-devDependencies

It is a monorepo using Yarn Workspace with the structrue like this:

After running yarn install on root folder, I find another version of module typescript installed inside tsutils dependency (at packages/web/node_modules/tsutils/node_modules/typescript), which causes error when linting my sourcecode in 'web' folder.

Standing at packages/web/node_modules/tsutils and executing yarn why typescript, it coldly replies:

[1/4] Why do we have the module 'typescript'..?
[2/4] Initialising dependency graph..
[3/4] Finding dependency..
[4/4] Calculating file sizes..
=> Found 'typescript@3.0.0-rc'
info Has been hoisted to 'typescript'
info This module exists because it's specified in 'devDependencies'.

I think the issue is here:

info This module exists because it's specified in 'devDependencies'.

Hi, what is your guess about this issue?

Hey @hirikarate sorry for the very slow reply. This got lost in my hundreds of Github notifications 😞

I don't think this has anything to do with devDependencies. The typescript that ends up in packages/web/node_modules/tsutils/node_modules/typescript shouldn't be there. Yarn even seems to know that from the yarn why and yarn list that don't even show it.

Interestingly, if you remove package/rest or remove rest's dependency on a different version of typescript, then yarn install again, the packages/web/node_modules/tsutils/node_modules/typescript folder will not be created. This must be some weird dependency resolution bug or something.

I'll try to debug into it as I find time..

Side note, i think yarn why typescript when you are in packages/web/node_modules/tsutils is basing it's listing on what it finds in tsutils's package.json, but in reality the typescript that is in that directory isn't even 3.0.0-rc, it is 2.9.2.

In mean time, my last resort is to remove the troublesome typescript with script

New site license keys for NVivo 11 Plus and NVivo 10 Posted on April 6, 2016 April 6, 2016 by Shalin Hai-Jew Kansas State University has new site license keys for NVivo 11 Plus and NVivo 10 to cover access through April 2017. NVIVO 11 Pro Free Download is a useful application that can be used for assessing the qualitative data. This application can be used for importing in addition to analyzing the files, images, PDFs, audio, video in addition to web pages. NVivo 11.4.0 Full Crack Free Download. Click on below link button to start NVivo 11.4.0 Crack free download. This is a full offline standalone setup of NVivo 11.4.0 Keygen for mac download. Posts about NVivo 11 Pro Download key written by Cracked Download. After installation copy the Crack for NVivo 11 Pro from the Crack folder. [disable internet!!!] For every Operating Sistem you have, you MUST run the ActivationPatch for NVivo 11 Pro available in the Crack folder in order to enusre compatibility, or it will cause instability.

Thank you for your time.

Ran into same problem with monorepo setup with Lerna and Yarn workspaces. After upgrading Typescript to 3.5.1, tslint stopped working.
@hirikarate workaround helps for the time being.