you don't have to create new PRs when revising. you can just push a commit to your branch, and it should automatically reflect here.

@bugzpodder But i had to change pr branch from master to next ..
#4700

💯

This PR needs a little clean up consider to follow this https://github.com/facebook/create-react-app/pull/4314/files

This is by the creators of Reactstrap

What's the difference aside from gist's contents?

@bugzpodder You don't need to specify the version 4 like bootstrap@4 . Bootstrap is currently on 4.1 soon 4.2 even reactstrap https://reactstrap.github.io/ site recommend just installing bootstrap without specify version number. The problem is that will always fallback on bootstrap@4 similar to previous one bootstrap@3.

I think reason the 4 is there bootstrap@4 the person copied the existing and just swapped out bootstrap keyword to reactstrap.

Go ahead and copy that PR it should take care of all issues

We want to be intentional about the version. The @4 will stay; people still actively use 3 so being explicit never hurts for clarity.

@Timer Sure, you're the boss here, I still think you shouldn't have to specify a version number.