|
1 | 1 | # Change Log |
2 | 2 |
|
| 3 | +## [1.1.0] 2021-03-19 |
| 4 | +### Bug fixing |
| 5 | +- Rename `master` branch to `main` |
| 6 | +- To make a lot of our changes, we've followed the instructions from here (minus the `colors` and `font-sizes`): https://tailwindcss.com/docs/upgrading-to-v2 |
| 7 | + - 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}` |
| 8 | + - After that, we've changed `{type}-blueGray-{number}` to `{type}-blueGray-{lower-number}`, i.e. (`100` became `50`, `200` became `100`, ..., `900` became `800`) |
| 9 | + - You can achieve this, by search in your whole project for `blueGray-100` and replace it with `blueGray-50` |
| 10 | + - Then, you search in your whole project for `blueGray-200` and replace it with `blueGray-100` |
| 11 | + - Then, you search in your whole project for `blueGray-300` and replace it with `blueGray-200` |
| 12 | + - Then, you search in your whole project for `blueGray-400` and replace it with `blueGray-300` |
| 13 | + - Then, you search in your whole project for `blueGray-500` and replace it with `blueGray-400` |
| 14 | + - Then, you search in your whole project for `blueGray-600` and replace it with `blueGray-500` |
| 15 | + - Then, you search in your whole project for `blueGray-700` and replace it with `blueGray-600` |
| 16 | + - Then, you search in your whole project for `blueGray-800` and replace it with `blueGray-700` |
| 17 | + - Then, you search in your whole project for `blueGray-900` and replace it with `blueGray-800` |
| 18 | + - 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}` |
| 19 | + - 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}` |
| 20 | +- `lg:bg-transparent` is not working anymore, so we've changed it with `lg:bg-opacity-0` |
| 21 | +- Since we've dropped the usage of custom CSS, and reverted to `Built-In CSS Support` from `NextJS`, we had to move our images inside the `public` folder, and our styles inside the `styles` folder |
| 22 | + - All the `require` images have been replaced by simple `/img/` strings |
| 23 | +- https://github.com/creativetimofficial/notus-angular/issues/4 |
| 24 | +- https://github.com/creativetimofficial/notus-js/issues/4 |
| 25 | +- https://github.com/creativetimofficial/notus-js/pull/5 |
| 26 | +- https://github.com/creativetimofficial/notus-js/pull/6 |
| 27 | +- https://github.com/creativetimofficial/notus-nextjs/issues/6 |
| 28 | +- https://github.com/creativetimofficial/notus-nextjs/issues/7 |
| 29 | +- https://github.com/creativetimofficial/notus-nextjs/issues/8 |
| 30 | +- https://github.com/creativetimofficial/notus-react/issues/3 |
| 31 | +- https://github.com/creativetimofficial/notus-svelte/issues/3 |
| 32 | +- https://github.com/creativetimofficial/notus-svelte/issues/6 |
| 33 | +- https://github.com/creativetimofficial/vue-notus/pull/4/ |
| 34 | +### Major style changes |
| 35 | +- 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: |
| 36 | + - https://blog.tailwindcss.com/tailwindcss-v2 |
| 37 | + - https://tailwindcss.com/ |
| 38 | + - https://tailwindcss.com/docs/upgrading-to-v2 |
| 39 | +### Deleted components |
| 40 | +- `next.config.js` (we do not need it anymore since we now use `Built-In CSS Support` from `NextJS`) |
| 41 | + - for the absolute imports, we've used the `jsconfig.json` file |
| 42 | +### Added components |
| 43 | +- `jsconfig.json` (to keep our absolute imports) |
| 44 | +### Deleted dependencies |
| 45 | +- `@tailwindcss/custom-forms` |
| 46 | +- `react-google-maps` (replaced by simple Google Maps API) |
| 47 | +- `@types/googlemaps` (dependencies of `react-google-maps`) |
| 48 | +- `@types/markerclustererplus` (dependencies of `react-google-maps`) |
| 49 | +- `@types/react` (dependencies of `react-google-maps`) |
| 50 | +- `@zeit/next-css` (we'll use the default `Built-In CSS Support` from `NextJS`) |
| 51 | +- `@zeit/next-sass` (we'll use the default `Built-In CSS Support` from `NextJS`) |
| 52 | +- `node-sass` (we'll use the default `Built-In CSS Support` from `NextJS`) |
| 53 | +- `next-images` (we'll use the default `Built-In CSS Support` from `NextJS`) |
| 54 | +- `next-fonts` (we'll use the default `Built-In CSS Support` from `NextJS`) |
| 55 | +- `next-compose-plugins` (we'll use the default `Built-In CSS Support` from `NextJS`) |
| 56 | +- `path` (we'll use the default `Built-In CSS Support` from `NextJS`) |
| 57 | +- `webpack` (we'll use the default `Built-In CSS Support` from `NextJS`) |
| 58 | +### Added dependencies |
| 59 | +- `@tailwindcss/forms` (replaces `@tailwindcss/custom-forms`) |
| 60 | +- `autoprefixer` |
| 61 | +- `postcss` |
| 62 | +### Updated dependencies |
| 63 | +``` |
| 64 | +@fortawesome/fontawesome-free 5.14.0 → 5.15.3 |
| 65 | +@popperjs/core 2.5.1 → 2.9.1 |
| 66 | +chart.js 2.9.3 → 2.9.4 |
| 67 | +next 9.5.3 → 10.0.9 |
| 68 | +react 16.13.1 → 17.0.1 |
| 69 | +@types/react 16.9.49 → 17.0.3 |
| 70 | +react-dom 16.13.1 → 17.0.1 |
| 71 | +react-scripts 3.4.3 → 4.0.3 |
| 72 | +tailwindcss 1.8.10 → 2.0.4 |
| 73 | +typescript 4.0.3 → 4.2.3 |
| 74 | +``` |
| 75 | +### Warning |
| 76 | +_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._ |
| 77 | + |
3 | 78 | ## [1.0.0] 2020-09-29 |
4 | 79 | ### Original Release |
5 | 80 | - Started project from [Tailwind Starter Kit by Creative Tim](https://www.creative-tim.com/learning-lab/tailwind-starter-kit/presentation?ref=nnjs-changelog) |
|
0 commit comments