thecodejack

sure. It makes sense to update the peer dependancies. I will do that. But the part I don't understand is why should this be a breaking change? I mean any...

Ok. I see it failing if deps are mentioned this way ``` "react": "16.3.0", "reactstrap": "^8.2.0" ``` Is it worth making a major release for this?

@TheSharpieOne Have updated peer dependencies via https://github.com/reactstrap/reactstrap/pull/1742/commits/e64b1991b9fd32ec0ad3aab12af0f548b183ed8f

@TheSharpieOne Do I need to do anything for this PR or it's waiting for Major release?

Hey @Tal500 Sorry. Was occupied with personal stuff. Will be looking into this today.

> BTW I recommend seeing the newly published library [leveluptuts/bookit](https://github.com/leveluptuts/bookit), though it's still experimental. I like their folder structure. All component files are placed in package folder.

> > BTW I recommend seeing the newly published library [leveluptuts/bookit](https://github.com/leveluptuts/bookit), though it's still experimental. > > I like their folder structure. All component files are placed in package folder....

@Tal500 Also note that I might have to remove pnpm usage as I don't use it any repos. It's great but just for one repo can't have another node modules...

My point is about global cache directories. pnpm AFAIK manages it's own like npm and yarn.

it's not for global use. cache directories are where you have a copy stored. When you do npm install, cache directory is where npm/pnpm searches first later downloads from internet...