- Rename
master
branch tomain
- To make a lot of our changes, we've followed the instructions from here (minus the
colors
andfont-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.js
files, 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. (100
became50
,200
became100
, ...,900
became800
)- You can achieve this, by search in your whole project for
blueGray-100
and replace it withblueGray-50
- Then, you search in your whole project for
blueGray-200
and replace it withblueGray-100
- Then, you search in your whole project for
blueGray-300
and replace it withblueGray-200
- Then, you search in your whole project for
blueGray-400
and replace it withblueGray-300
- Then, you search in your whole project for
blueGray-500
and replace it withblueGray-400
- Then, you search in your whole project for
blueGray-600
and replace it withblueGray-500
- Then, you search in your whole project for
blueGray-700
and replace it withblueGray-600
- Then, you search in your whole project for
blueGray-800
and replace it withblueGray-700
- Then, you search in your whole project for
blueGray-900
and 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.js
files, 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.js
files, 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-transparent
is not working anymore, so we've changed it withlg:bg-opacity-0
- Since we've dropped the usage of custom CSS, and reverted to
Built-In CSS Support
fromNextJS
, we had to move our images inside thepublic
folder, and our styles inside thestyles
folder- All the
require
images have been replaced by simple/img/
strings
- All the
- creativetimofficial/notus-angular#4
- creativetimofficial/notus-js#4
- creativetimofficial/notus-js#5
- creativetimofficial/notus-js#6
- creativetimofficial#6
- creativetimofficial#7
- creativetimofficial#8
- creativetimofficial/notus-react#3
- creativetimofficial/notus-svelte#3
- creativetimofficial/notus-svelte#6
- creativetimofficial/vue-notus#4
- 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:
next.config.js
(we do not need it anymore since we now useBuilt-In CSS Support
fromNextJS
)- for the absolute imports, we've used the
jsconfig.json
file
- for the absolute imports, we've used the
jsconfig.json
(to keep our absolute imports)
@tailwindcss/custom-forms
react-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
)@zeit/next-css
(we'll use the defaultBuilt-In CSS Support
fromNextJS
)@zeit/next-sass
(we'll use the defaultBuilt-In CSS Support
fromNextJS
)node-sass
(we'll use the defaultBuilt-In CSS Support
fromNextJS
)next-images
(we'll use the defaultBuilt-In CSS Support
fromNextJS
)next-fonts
(we'll use the defaultBuilt-In CSS Support
fromNextJS
)next-compose-plugins
(we'll use the defaultBuilt-In CSS Support
fromNextJS
)path
(we'll use the defaultBuilt-In CSS Support
fromNextJS
)webpack
(we'll use the defaultBuilt-In CSS Support
fromNextJS
)
@tailwindcss/forms
(replaces@tailwindcss/custom-forms
)autoprefixer
postcss
@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
next 9.5.3 → 10.0.9
react 16.13.1 → 17.0.1
@types/react 16.9.49 → 17.0.3
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
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.
- Started project from Tailwind Starter Kit by Creative Tim
- Added design from Tailwind Starter Kit by Creative Tim