Releases: creativetimofficial/notus-react
Releases · creativetimofficial/notus-react
Updated dependencies
[1.1.0] 2021-03-19
Bug fixing
- Rename
masterbranch tomain - To make a lot of our changes, we've followed the instructions from here (minus the
colorsandfont-sizes): https://tailwindcss.com/docs/upgrading-to-v2- For the colors, the only change that we made, is the fact that we've added all Tailwind CSS colors to our
tailwind.config.jsfiles, and inside our product, all{type}-gray-{number}classes were renamed to{type}-blueGray-{number} - After that, we've changed
{type}-blueGray-{number}to{type}-blueGray-{lower-number}, i.e. (100became50,200became100, ...,900became800)- You can achieve this, by search in your whole project for
blueGray-100and replace it withblueGray-50 - Then, you search in your whole project for
blueGray-200and replace it withblueGray-100 - Then, you search in your whole project for
blueGray-300and replace it withblueGray-200 - Then, you search in your whole project for
blueGray-400and replace it withblueGray-300 - Then, you search in your whole project for
blueGray-500and replace it withblueGray-400 - Then, you search in your whole project for
blueGray-600and replace it withblueGray-500 - Then, you search in your whole project for
blueGray-700and replace it withblueGray-600 - Then, you search in your whole project for
blueGray-800and replace it withblueGray-700 - Then, you search in your whole project for
blueGray-900and replace it withblueGray-800
- You can achieve this, by search in your whole project for
- For the colors, the only change that we made, is the fact that we've added all Tailwind CSS colors to our
tailwind.config.jsfiles, and inside our product, all{type}-blue-{number}classes were renamed to{type}-lightBlue-{number} - For the colors, the only change that we made, is the fact that we've added all Tailwind CSS colors to our
tailwind.config.jsfiles, and inside our product, all{type}-green-{number}classes were renamed to{type}-emerald-{number}
- For the colors, the only change that we made, is the fact that we've added all Tailwind CSS colors to our
lg:bg-transparentis not working anymore, so we've changed it withlg:bg-opacity-0- creativetimofficial/notus-angular#4
- creativetimofficial/notus-js#4
- creativetimofficial/notus-js#5
- creativetimofficial/notus-js#6
- creativetimofficial/notus-nextjs#6
- creativetimofficial/notus-nextjs#7
- creativetimofficial/notus-nextjs#8
- #3
- creativetimofficial/notus-svelte#3
- creativetimofficial/notus-svelte#6
- creativetimofficial/vue-notus#4
Major style changes
- The upgrade of Tailwind CSS from version 1 to version 2, will cause multiple style changes, check them out on the official Tailwind CSS websites:
Deleted components
Added components
Deleted dependencies
@tailwindcss/custom-formsreact-google-maps(replaced by simple Google Maps API)@types/googlemaps(dependencies ofreact-google-maps)@types/markerclustererplus(dependencies ofreact-google-maps)@types/react(dependencies ofreact-google-maps)
Added dependencies
@tailwindcss/forms(replaces@tailwindcss/custom-forms)autoprefixerpostcss
Updated dependencies
@fortawesome/fontawesome-free 5.14.0 → 5.15.3
@popperjs/core 2.5.1 → 2.9.1
chart.js 2.9.3 → 2.9.4
react 16.13.1 → 17.0.1
react-dom 16.13.1 → 17.0.1
react-scripts 3.4.3 → 4.0.3
tailwindcss 1.8.10 → 2.0.4
typescript 4.0.3 → 4.2.3
Warning
On a clean install there may be some warnings from request, chokidar, fsevents - they come from node_modules, and they do not affect the product at all.
Initial release.
Merge pull request #1 from creativetimofficial/feature/v1.0.0 Feature: v1.0.0