Thierry-Chain / Library-Management-App

Updated Library management system
https://smart-library-rw.herokuapp.com
2 stars 1 forks source link

Update dependency react-toastify to v9 - autoclosed #100

Closed renovate[bot] closed 8 months ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react-toastify ^6.2.0 -> ^9.0.0 age adoption passing confidence

Release Notes

fkhadra/react-toastify (react-toastify) ### [`v9.1.3`](https://togithub.com/fkhadra/react-toastify/releases/tag/v9.1.3) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.1.2...v9.1.3) ### Release note - Add support for RSC (next app router): [#​951](https://togithub.com/fkhadra/react-toastify/issues/951) - Partially address `Toast is undefined || Uncaught TypeError: Cannot read properties of undefined (reading 'content')` [#​858](https://togithub.com/fkhadra/react-toastify/issues/858) [#​952](https://togithub.com/fkhadra/react-toastify/issues/952) - Bump dependencies ### [`v9.1.2`](https://togithub.com/fkhadra/react-toastify/releases/tag/v9.1.2) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.1.1...v9.1.2) ### Release notes Mainly bug fixes as I'm working on the next major release. #### πŸ•·Bugfixes - fix resetting options [#​921](https://togithub.com/fkhadra/react-toastify/issues/921) [#​920](https://togithub.com/fkhadra/react-toastify/issues/920) - fix autoClose on update [#​918](https://togithub.com/fkhadra/react-toastify/issues/918) - fix invalid CSS translate [#​925](https://togithub.com/fkhadra/react-toastify/issues/925) ### [`v9.1.1`](https://togithub.com/fkhadra/react-toastify/compare/v9.1.0...v9.1.1) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.1.0...v9.1.1) ### [`v9.1.0`](https://togithub.com/fkhadra/react-toastify/releases/tag/v9.1.0) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.0.8...v9.1.0) ### Release notes #### πŸš€ Features - `toast.promise` let you type `data` for each state. This is useful when rendering something based on the response. For example: ```tsx interface Success { username: string } interface Error { err: string } toast.promise(myPromise, { success: { render({ data }) { return data.username; } }, error: { render({ data }) { return data.err; } } }) ``` - `toast.update` accepts a generic as well to specify the data type ```tsx interface TData { username: string } toast.update(id, { data: payload, render({ data }) { return `hello ${data.username}` } }) ``` #### πŸ•· Bugfixes - fix progress countdown stops on mobile [#​580](https://togithub.com/fkhadra/react-toastify/issues/580) - prevent clash with ios native gesture [#​397](https://togithub.com/fkhadra/react-toastify/issues/397) - fix toast when a word is too long [#​864](https://togithub.com/fkhadra/react-toastify/issues/864) - fix missing types declarations in exports [#​843](https://togithub.com/fkhadra/react-toastify/issues/843) - fix `toast.done` not dismissing toast [#​853](https://togithub.com/fkhadra/react-toastify/issues/853) - fix cursor when close on click is false [#​839](https://togithub.com/fkhadra/react-toastify/issues/839) #### 🚨 Deprecated API Added deprecation notice for the API below. They will be removed in the next major release | API | Why | Alternative | |-----|-----|-------------| | `onClick` | Not used that much, it's increasing the API surface for nothing | Can easily be implemented in userland. Just render a react component and attach the handler to it. `toast(
hello
)` | | `onOpen` | Does not play well with `useEffect` behavior in react18 (runs twice in dev mode) see [#​741](https://togithub.com/fkhadra/react-toastify/issues/741) | A better approach is to use `toast.onChange` see https://fkhadra.github.io/react-toastify/listen-for-changes/ | | `onClose` | Does not play well with `useEffect` behavior in react18 (runs twice in dev mode) see [#​741](https://togithub.com/fkhadra/react-toastify/issues/741) | A better approach is to use `toast.onChange` see https://fkhadra.github.io/react-toastify/listen-for-changes/ | | `toast.POSITION` | Reduce bundle size :) | Thanks to typescript, we now have autocomplete | | `toast.TYPE` | Reduce bundle size :) | Thanks to typescript, we now have autocomplete | #### βš™οΈ Chore - bump dependencies - refactor internal ### [`v9.0.8`](https://togithub.com/fkhadra/react-toastify/releases/tag/v9.0.8) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.0.7...v9.0.8) ### Release notes #### 🐞Bugfixes - fix draggable in strict mode [#​752](https://togithub.com/fkhadra/react-toastify/issues/752) - fix sass import [#​771](https://togithub.com/fkhadra/react-toastify/issues/771) - fix progress bar overflow for WebKit browser(safari, ios...) [#​791](https://togithub.com/fkhadra/react-toastify/issues/791) - fix dismissed toasts while the container is unmounted still appear when the container is mounted [#​811](https://togithub.com/fkhadra/react-toastify/issues/811) - fix AutoClose doesn't work on update [#​810](https://togithub.com/fkhadra/react-toastify/issues/810) [#​782](https://togithub.com/fkhadra/react-toastify/issues/782) [#​720](https://togithub.com/fkhadra/react-toastify/issues/720) #### Chore - master branch renamed to main πŸ’– ### [`v9.0.7`](https://togithub.com/fkhadra/react-toastify/releases/tag/v9.0.7) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.0.6...v9.0.7) ### Release note #### Bugfix - fix memory leak when multiple containers are used [#​772](https://togithub.com/fkhadra/react-toastify/issues/772), thanks to [@​roblotter](https://togithub.com/roblotter) #### Chore - build artifacts are no longer minified. This was causing issues with some bundlers like vitejs [#​797](https://togithub.com/fkhadra/react-toastify/issues/797) ### [`v9.0.6`](https://togithub.com/fkhadra/react-toastify/releases/tag/v9.0.6) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.0.5...v9.0.6) ### Release note #### Bugfix - fix missing generic in `useNotificationCenter` typing [#​796](https://togithub.com/fkhadra/react-toastify/issues/796) ### [`v9.0.5`](https://togithub.com/fkhadra/react-toastify/releases/tag/v9.0.5) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.0.4...v9.0.5) ### Release note #### πŸ•· Bugfix - inject-style has now the correct file-name in bundle [#​779](https://togithub.com/fkhadra/react-toastify/issues/779) ### [`v9.0.4`](https://togithub.com/fkhadra/react-toastify/releases/tag/v9.0.4) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.0.3...v9.0.4) ### Release note This release does not work with CRA v4(2 years old) due to the lack of support for es modules. I strongly advise to upgrade to lastest CRA if possible. Alternative solution: - stick to v9.0.3 - update webpack config [https://github.com/reactioncommerce/reaction-component-library/issues/399](https://togithub.com/reactioncommerce/reaction-component-library/issues/399) #### Bugfix - use mjs extensions for es modules [#​767](https://togithub.com/fkhadra/react-toastify/issues/767) thank to [@​mikebarkmin](https://togithub.com/mikebarkmin) ### [`v9.0.3`](https://togithub.com/fkhadra/react-toastify/releases/tag/v9.0.3) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.0.2...v9.0.3) ### Release notes #### πŸ•· Bugfix - Fix icon not updating after calling `toast.update` [#​770](https://togithub.com/fkhadra/react-toastify/issues/770) ### [`v9.0.2`](https://togithub.com/fkhadra/react-toastify/releases/tag/v9.0.2) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.0.1...v9.0.2) ### Release notes Thanks to [@​Rambatino](https://togithub.com/Rambatino), [@​grit96](https://togithub.com/grit96), [@​Vl3oss](https://togithub.com/Vl3oss), [@​eolme](https://togithub.com/eolme) for this release #### πŸ•· Bug fixes - typo [#​764](https://togithub.com/fkhadra/react-toastify/issues/764) - pass toast styles through [#​763](https://togithub.com/fkhadra/react-toastify/issues/763) - add function type in icon prop [#​761](https://togithub.com/fkhadra/react-toastify/issues/761) - closeButton/icon types/rendering [#​758](https://togithub.com/fkhadra/react-toastify/issues/758) - fix empty data object in NotificationCenter [#​757](https://togithub.com/fkhadra/react-toastify/issues/757) ### [`v9.0.1`](https://togithub.com/fkhadra/react-toastify/compare/v9.0.0...v9.0.1) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v9.0.0...v9.0.1) ### [`v9.0.0`](https://togithub.com/fkhadra/react-toastify/releases/tag/v9.0.0) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v8.2.0...v9.0.0) ### Release note #### πŸš€ What is new in v9 Say hello to addons! What are addons? So, addons are like DLCs in video games but for react-toastify πŸ˜†. More seriously, you can think of it as utilities built around react-toastify. For example, custom theme, hooks, components etc... ##### useNotificationCenter The first addon that I would like to introduce is the `useNotificationCenter` headless hook! As the name suggests, it let you build your notification center on top of react-toastify. See for yourself πŸ‘‡ https://user-images.githubusercontent.com/5574267/166549174-48422a61-ff7b-4eeb-b53f-d903db3d1595.mov Another example using MUI. [![Edit mui-notification-center](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/mui-notification-center-zvxod3?fontsize=14\&hidenavigation=1\&theme=dark) Check the [documentation](/react-toastify/addons/use-notification-center) for more details. ##### Stacked toasts This second addon will be released later. There are a bunch of details that I need to cover and I don't want to release something too buggy. Nevertheless, I'm really excited about it and I think it's worth showcasing anyway. I call it `StackedContainer` for now, it's an alternative to the `ToastContainer` component. ![stacked-container](https://user-images.githubusercontent.com/5574267/160688000-1d01d949-d9e1-41f4-858c-f5c9a33b901d.gif) #### πŸ’₯ Breaking changes There are 2 breaking changes. The API change for `toast.onChange` and the removal of `toast.configure`. ##### `toast.onChange` The previous API was returning the `numberOfToastDisplayed` and the `containerId`. Honestly, this API seems to be incomplete. For example, with the old API, if I wanted to do some logging this would be very difficult because I don't have enough data to log. ```tsx toast.onChange((numberOfToastDisplayed, containerId) => { logger.info("nothing useful to log, ...") }) ``` The new API offers more possibilities. The callback will receive a `ToastItem`. The item provides a bunch of useful properties `status`, `content`, `id`, `data`, etc... ```jsx interface ToastItem { id: Id; content: React.ReactNode; theme?: Theme; type?: TypeOptions; isLoading?: boolean; containerId?: Id; data: Data; icon?: React.ReactNode | false; status: "added" | "removed" | "updated" } const unsubscribe = toast.onChange((payload: ToastItem) => { switch (payload.status) { case "added": // new toast added break; case "updated": // toast updated break; case "removed": // toast has been removed break; } }); ``` For example, if I want to log something every time there is a new error notification, with the new API it's trivial ```tsx toast.onChange(payload => { if(payload.status === "added" && payload.type === toast.TYPE.ERROR) { logger.error({ createdAt: Date.now(), content: payload.content, data: payload.data }) } }) ``` ##### `toast.configure` removal `toast.configure` works fine for most cases but the current implementation has one main issue. It does not work with react context because it creates a new react tree. That being said, having 2 APIs to do the same thing is a bad thing. #### πŸ•· Bug fixes - [#​725](https://togithub.com/fkhadra/react-toastify/issues/725) the success toast on promise does not disappear when resolving too quickly - [#​711](https://togithub.com/fkhadra/react-toastify/issues/711) updated toast sometimes has wrong styles - [#​700](https://togithub.com/fkhadra/react-toastify/issues/700) generics are not used for toast.promise's result type if you use a custom render method ### [`v8.2.0`](https://togithub.com/fkhadra/react-toastify/releases/tag/v8.2.0) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v8.1.1...v8.2.0) ### Release note - add deprecation notice for `toast.configure`. - add deprecation notice for `toast.onChange`. API for this method will change in the next major release #### πŸ•· Bugfixes - fix [#​707](https://togithub.com/fkhadra/react-toastify/issues/707) Promise toast does not close automatically if promise resolves too quickly #### βš™οΈ Chore - bump parcel to latest version ### [`v8.1.1`](https://togithub.com/fkhadra/react-toastify/releases/tag/v8.1.1) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v8.1.0...v8.1.1) ### Release notes #### πŸ•· Bug fixes - fix [#​702](https://togithub.com/fkhadra/react-toastify/issues/702) autoClose duration start after the entrance animation finish - fix [#​689](https://togithub.com/fkhadra/react-toastify/issues/689) prevents promise without success to hang on to the pending state - fix [#​645](https://togithub.com/fkhadra/react-toastify/issues/645) and [#​618](https://togithub.com/fkhadra/react-toastify/issues/618) `onClose` now work as expected! - fix [#​694](https://togithub.com/fkhadra/react-toastify/issues/694) Fix error in Chrome: remove preventDefault from passive listener #### βš™οΈ Chore - [#​703](https://togithub.com/fkhadra/react-toastify/issues/703) the `ToastPromiseParams` is now exported - exit animation on safari are not conflicting with drag transition anymore Thanks to [@​03c](https://togithub.com/03c), [@​wilson-webdev](https://togithub.com/wilson-webdev), [@​essential-randomness](https://togithub.com/essential-randomness) for their contributions ### [`v8.1.0`](https://togithub.com/fkhadra/react-toastify/releases/tag/v8.1.0) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v8.0.3...v8.1.0) ### Release notes πŸš€ Features - add support for optional stages in promise [#​646](https://togithub.com/fkhadra/react-toastify/issues/646) ### [`v8.0.3`](https://togithub.com/fkhadra/react-toastify/releases/tag/v8.0.3) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v8.0.2...v8.0.3) ### Release notes #### 🐞 Bugfixes - fix text-align has not effect on content [#​657](https://togithub.com/fkhadra/react-toastify/issues/657) - fix disabling icon individually [#​658](https://togithub.com/fkhadra/react-toastify/issues/658) - fix tree shaking [#​641](https://togithub.com/fkhadra/react-toastify/issues/641) ### [`v8.0.2`](https://togithub.com/fkhadra/react-toastify/releases/tag/v8.0.2) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v8.0.1...v8.0.2) ### Release Notes #### Bugfix - fix [#​635](https://togithub.com/fkhadra/react-toastify/issues/635) Icon on safari not displayed ### [`v8.0.1`](https://togithub.com/fkhadra/react-toastify/releases/tag/v8.0.1) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v8.0.0...v8.0.1) ### Release notes #### Features - `toast.promise` accept function that returns a promise. ### [`v8.0.0`](https://togithub.com/fkhadra/react-toastify/releases/tag/v8.0.0) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v7.0.4...v8.0.0) React-toastify has been around for 5 years(will turn five the 8 November πŸŽ‚). Since the beginning, one of the goals was to provide a library that is highly customizable and also able to work out of the box. Every major release introduces breaking changes but this is for the best πŸ‘Œ. ![React toastify](https://user-images.githubusercontent.com/5574267/130804494-a9d2d69c-f170-4576-b2e1-0bb7f13dd92d.gif "React toastify") #### πŸš€ Features ##### New look Notifications of different types (`toast.info`, `toast.error`, `toast.success`, `toast.warning`) display an icon associated with the selected type. You can also notice that the progress bar color matches the type color.
v8-icons-light v8-icons-dark v8-icons-colored
Don't be afraid 😱, if you don't like those icons you can use your own or remove them. This is what it looks like in practice. ```tsx toast("Default toast behavior is untouched, no icon to display"); toast.info("Lorem ipsum dolor"); // same as toast(message, {type: "info"}); toast.error("Lorem ipsum dolor") toast.success("Lorem ipsum dolor") toast.warn("Lorem ipsum dolor") toast.error("Without icon", { icon: false }); toast.success("You can provide any string", { icon: "πŸš€" }); // custom icons have access to the theme and the toast type toast.success("And of course a component of your choice", { icon: MyIcon }); toast.success("Even a function, given you return something that can be rendered", { icon: ({theme, type}) => }); //Disable icons ``` ##### Clear separation between type and theme Prior to v8, `toast.info`, `toast.error`, etc... Would display respectively a blue notification, a red notification, etc... This is not the case anymore. There are 3 distinct themes: `light`, `dark`, `colored`. The theme can be applied globally or per notification. ```tsx //Set the theme globally // define per toast toast.info("Display a dark notification of type info"); toast.info("Display a light notification of type info", { theme: "light" }); toast.info("Display a blue notification of type info", { theme: "colored" }); ``` This separation will benefit theming in the future. ##### I promise this is new, I'll tell you if you await v8-promise v8-promise-resolved The library exposes a `toast.promise` function. Supply a promise and the notification will be updated if it resolves or fails. When the promise is pending a spinner is displayed. Again you hide it, I bet you already know how toπŸ˜†. Let's start with a simple example ```tsx const resolveAfter3Sec = new Promise(resolve => setTimeout(resolve, 3000)); toast.promise( resolveAfter3Sec, { pending: 'Promise is pending', success: 'Promise resolved πŸ‘Œ', error: 'Promise rejected 🀯' } ) ``` Displaying a simple message is what you would want to do in 90% of cases. But what if the message you want to display depends on the promise response, what if you want to change some options for the error notification? Rest assured, under the hood, the library uses `toast.update`. Thanks to this, you have full control over each notification. ```tsx const resolveWithSomeData = new Promise(resolve => setTimeout(() => resolve("world"), 3000)); toast.promise( resolveAfter3Sec, { pending: 'Promise is pending', success: { render({data}){ return `Hello ${data}` }, // other options icon: "🟒", }, error: { render({data}){ // When the promise reject, data will contains the error return } } } ) ``` If you want to take care of each step yourself you can use `toast.loading` and update the notification yourself. ```tsx const id = toast.loading("Please wait...") //do something else toast.update(id, { render: "All is good", type: "success" }); ``` ##### Pass data even when you are not rendering a react component One way to pass data to the notification was to use the context api or provide your own component. Starting v8 a `data` option is now available to make it easier. ```tsx toast(({data}) => `Hello ${data}`, { data: "world" }) ``` ##### I just want to change few colors Most of the time, users are ok with the default style, they just want to change some colors to match their brand. I think one way to improve the DX for all of us is to embrace CSS variables. That's why the library has switched to css variables! All you want is to change the color of the progress bar? No problem ```css :root{ // this is the default value below --toastify-color-progress-light: linear-gradient( to right, #​4cd964, #​5ac8fa, #​007aff, #​34aadc, #​5856d6, #ff2d55 ); } ``` You can find the list of all exposed variables [here](https://fkhadra.github.io/react-toastify/how-to-style.md#override-css-variables) #### πŸ’₯ Breaking changes There are few breaking changes. - The separation between theme and type. The type `dark` has been removed ```tsx // before v8 toast("hello", { type: "dark" }) // toast.TYPE.DARK is no longer available // in v8 toast("hello", { theme: "dark" }) // or toast.dark("hello") ``` - Notifications of different types are not colored by default, but they look pretty by default now πŸ˜†. You can use the `colored` theme to get the same behavior as the previous version ```tsx toast.info("hello", { theme: "colored" }) // or apply the theme globally ``` - An icon is displayed by default for the notificaiton of type `info`, `error`, `warning`, `success` ```tsx // to opt-out gloablly from this behavior // or per toast toast.info("hello", { icon: false }); ``` - the following css classes has been removed ```css .Toastify__toast--dark { } .Toastify__toast--default { } .Toastify__toast--info { } .Toastify__toast--success { } .Toastify__toast--warning { } .Toastify__toast--error { } ``` #### βš™οΈ Chore - update all dependencies That's it for this release. Thank you for using react-toastify and happy coding! ### [`v7.0.4`](https://togithub.com/fkhadra/react-toastify/releases/tag/v7.0.4) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v7.0.3...v7.0.4) ### Release notes #### πŸ› Bugfix - fix [#​572](https://togithub.com/fkhadra/react-toastify/issues/572) flex layout issue(regression) - fix [#​577](https://togithub.com/fkhadra/react-toastify/issues/577) border-radius in mobile is not 0. Thanks to [@​mateuszpigula](https://togithub.com/mateuszpigula) - fix [#​481](https://togithub.com/fkhadra/react-toastify/issues/481) clearWaitingQueue not working - fix [#​589](https://togithub.com/fkhadra/react-toastify/issues/589) accessibility issues with progressbar #### Chore - bump dependencies ### [`v7.0.3`](https://togithub.com/fkhadra/react-toastify/releases/tag/v7.0.3) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v7.0.2...v7.0.3) ### Release notes #### πŸ› Bugfix - fix [#​561](https://togithub.com/fkhadra/react-toastify/issues/561) missing declaration file ### [`v7.0.2`](https://togithub.com/fkhadra/react-toastify/releases/tag/v7.0.2) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v7.0.1...v7.0.2) ### Release note #### πŸ› Bugfix - fix [#​560](https://togithub.com/fkhadra/react-toastify/issues/560) when using limit, new toast is displayed only when exit animation is done. ### [`v7.0.1`](https://togithub.com/fkhadra/react-toastify/releases/tag/v7.0.1) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v7.0.0...v7.0.1) ### Release notes #### πŸ› Bugfix - Closing animation showing twice if dismiss is called after a very short time after showing the toast [#​559](https://togithub.com/fkhadra/react-toastify/issues/559) ### [`v7.0.0`](https://togithub.com/fkhadra/react-toastify/releases/tag/v7.0.0) [Compare Source](https://togithub.com/fkhadra/react-toastify/compare/v6.2.0...v7.0.0) ### Release Notes #### πŸ’₯ Breaking changes - dependency to react-transition-group has been removed [#​514](https://togithub.com/fkhadra/react-toastify/issues/514) - the `duration` parameter has been removed from `cssTransition`. Css animations just works now out of the box. Check the codesanbox below - the border-radius has been increased a bit #### πŸš€ Features - Css animation just works! [![View](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/react-toastify-animatecss-jxrx9?fontsize=14\&hidenavigation=1\&theme=dark\&view=preview) - add a way to load the CSS without a CSS loader [![Edit react-toastify-inject-style](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/react-toastify-inject-style-qfg0l?fontsize=14\&hidenavigation=1\&theme=dark) - specify swipe direction, close [#​512](https://togithub.com/fkhadra/react-toastify/issues/512) . Thanks to [@​denydavy](https://togithub.com/denydavy) [![Edit react-toastify-drag-y](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/react-toastify-drag-y-lh88i?fontsize=14\&hidenavigation=1\&theme=dark) - bundle size reduced from ~7k to ~5k! - remove the dependency on prop-types. #### πŸ› Bugfix - fix [#​541](https://togithub.com/fkhadra/react-toastify/issues/541) apply pauseOnFocusLoss on first render - fix [#​538](https://togithub.com/fkhadra/react-toastify/issues/538) react-dom should be a peer dep - fix [#​530](https://togithub.com/fkhadra/react-toastify/issues/530) change id generation - fix [#​534](https://togithub.com/fkhadra/react-toastify/issues/534) [#​483](https://togithub.com/fkhadra/react-toastify/issues/483) toastId cannot be reused - fix [#​511](https://togithub.com/fkhadra/react-toastify/issues/511) by removing react-transition-group - fix [#​550](https://togithub.com/fkhadra/react-toastify/issues/550) Unable to select text inside inputs when a toast is open - fix [#​555](https://togithub.com/fkhadra/react-toastify/issues/555) The toast timer starts after you click on the toast

Configuration

πŸ“… Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

β™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

πŸ”• Ignore: Close this PR and you won't be reminded about this update again.



This PR has been generated by Mend Renovate. View repository job log here.

vercel[bot] commented 1 year ago

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Comments Updated (UTC)
manage-my-library βœ… Ready (Inspect) Visit Preview πŸ’¬ Add feedback Dec 1, 2023 6:00am