Closed renovate[bot] closed 8 months ago
vercel[bot]
commented
8 months ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| staked-celo-web-app | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jan 18, 2024 2:02pm |
socket-security[bot]
commented
8 months ago Updated dependencies detected. Learn more about Socket for GitHub ↗︎
| Packages | Version | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|---|
| react-number-format | 4.9.3...5.3.1 | None | +0/-0 |
250 kB | sudhanshu |
github-actions[bot]
commented
8 months ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
The following page changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/[...slug] |
12.26 KB |
524.16 KB | 149.76% (🟡 +0.06%) |
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
renovate[bot]
commented
8 months ago Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.
github-actions[bot]
commented
8 months ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
The following page changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/[...slug] |
12.26 KB |
524.3 KB | 149.80% (🟡 +0.06%) |
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
github-actions[bot]
commented
8 months ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
The following page changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/[...slug] |
12.26 KB |
524.3 KB | 149.80% (🟡 +0.06%) |
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
This PR contains the following updates:
^4.9.3->^5.0.0Release Notes
s-yadav/react-number-format (react-number-format)
### [`v5.3.1`](https://togithub.com/s-yadav/react-number-format/releases/tag/v5.3.1): Bug fixes [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v5.3.0...v5.3.1) - Fix infinite rerender when values.value is used valueIsNumericString not provided. [#786](https://togithub.com/s-yadav/react-number-format/issues/786) - Fix for delete of decimalSeparator happening when fixeDecimalScale is set. [#789](https://togithub.com/s-yadav/react-number-format/issues/789) ### [`v5.3.0`](https://togithub.com/s-yadav/react-number-format/releases/tag/v5.3.0): Bug fixes with NumberFormatBase API improvement. [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v5.2.2...v5.3.0) - Fix [https://github.com/s-yadav/react-number-format/issues/774](https://togithub.com/s-yadav/react-number-format/issues/774) - Added support to inform rnf to treat two character as same. - Fix custom numeral example - Documentation improvement, [@gregfenton](https://togithub.com/gregfenton), [@minervabot](https://togithub.com/minervabot) ### [`v5.2.2`](https://togithub.com/s-yadav/react-number-format/releases/tag/v5.2.2): Bug fixes [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v5.2.1...v5.2.2) - Fix for prop values on not updating (not reflecting on input) on StrictMode. Regression of v5.2.0 - fix(number_format_base): prevent warnings in SRR when using useLayoutEffect. by [@NicolasMontone](https://togithub.com/NicolasMontone) ### [`v5.2.1`](https://togithub.com/s-yadav/react-number-format/releases/tag/v5.2.1): Regression fix from 5.2.0 [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v5.2.0...v5.2.1) Regression fix: try to correct the value if the old formatted value is provided but the format prop changes ### [`v5.2.0`](https://togithub.com/s-yadav/react-number-format/releases/tag/v5.2.0): Bug fixes and valueIsNumericString prop improvement. [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v5.1.4...v5.2.0) **Improvements** - Optimize rendering, and avoid multiple rerender when number format is mounted. - Try to guess valueIsNumericString based on props and value, so the user no longer has to define this prop, if the format prop (prefix/ suffix for numeric format, format prop for pattern format) doesn't have the number in it. **Fixes** - Fixes [#736](https://togithub.com/s-yadav/react-number-format/issues/736) - Fix for focus on mount getting reset. - Fixed [#740](https://togithub.com/s-yadav/react-number-format/issues/740) - fixed type for the format, removeFormat, getCaretBoundary. - Fixed [#741](https://togithub.com/s-yadav/react-number-format/issues/741) - Thousand and decimal formatting broken while typing when value isNumericString is set to false - Fixed [#742](https://togithub.com/s-yadav/react-number-format/issues/742) - cursor position getting changed when format props are updated during typing. - Fixed [#725](https://togithub.com/s-yadav/react-number-format/issues/725) - The cursor position not being correct when allowed decimal separator is typed - Fixed a couple of false positive tests and some regressions around those. ### [`v5.1.4`](https://togithub.com/s-yadav/react-number-format/releases/tag/v5.1.4): Bug fixes [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v5.1.3...v5.1.4) - Fixed [#694](https://togithub.com/s-yadav/react-number-format/issues/694) Prefix/Suffix containing numbers gets appended to value. - Fixed [#691](https://togithub.com/s-yadav/react-number-format/issues/691) Prefix/Suffix blocking input when set to a number - Fixed [#729](https://togithub.com/s-yadav/react-number-format/issues/729) Prefix '-' does not allow to remove first number - Added fixedDecimalScale prop to doc [#735](https://togithub.com/s-yadav/react-number-format/issues/735) by [@arminbashizade](https://togithub.com/arminbashizade) ### [`v5.1.3`](https://togithub.com/s-yadav/react-number-format/releases/tag/v5.1.3): Bug fixes [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v5.1.2...v5.1.3) - Fixed [#712](https://togithub.com/s-yadav/react-number-format/issues/712) (Extra character added if you start typing from start of the input while input is fully filled) - Fixed [#711](https://togithub.com/s-yadav/react-number-format/issues/711) (The caret is not moved when typing a decimal separator at an existing decimal separator) - Mark module as side effect free ([#713](https://togithub.com/s-yadav/react-number-format/issues/713) by [@topaxi](https://togithub.com/topaxi) ) - pass type parameter to SyntheticEvent in event source object. ([#703](https://togithub.com/s-yadav/react-number-format/issues/703) by [@yukiyokotani](https://togithub.com/yukiyokotani) ) ### [`v5.1.2`](https://togithub.com/s-yadav/react-number-format/compare/v5.1.1...v5.1.2) [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v5.1.1...v5.1.2) ### [`v5.1.1`](https://togithub.com/s-yadav/react-number-format/releases/tag/v5.1.1): Bug fixes [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v5.1.0...v5.1.1) - Fixed typo on patternFormatter export. [#698](https://togithub.com/s-yadav/react-number-format/issues/698) - Fixed cursor position getting reset if isAllowed returns false. [#699](https://togithub.com/s-yadav/react-number-format/issues/699) - Fixed doc for isAllowed prop. [#697](https://togithub.com/s-yadav/react-number-format/issues/697) by [@3794](https://togithub.com/3794) ### [`v5.1.0`](https://togithub.com/s-yadav/react-number-format/releases/tag/v5.1.0): Bug fixes [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v5.0.1...v5.1.0) - Fixed [#652](https://togithub.com/s-yadav/react-number-format/issues/652) - Fixed [#695](https://togithub.com/s-yadav/react-number-format/issues/695) - Added isValidInputCharacter in NumberFormatBase to figure out if a character is allowed to be typed. This mostly used internally by NumericFormat, but exposed to NumberFormatBase, if customization is needed. ### [`v5.0.1`](https://togithub.com/s-yadav/react-number-format/releases/tag/v5.0.1): Bug fixes [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v5.0.0...v5.0.1) - Fixed [https://github.com/s-yadav/react-number-format/issues/679](https://togithub.com/s-yadav/react-number-format/issues/679) ([@louismariegaborit](https://togithub.com/louismariegaborit)) - Fixed [https://github.com/s-yadav/react-number-format/issues/678](https://togithub.com/s-yadav/react-number-format/issues/678) - Return all required props for NumberFormatBase from useNumericFormat and usePatternFormat hooks ### [`v5.0.0`](https://togithub.com/s-yadav/react-number-format/releases/tag/v5.0.0): Major Release (v5) - React Number Format rewrite [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v4.9.4...v5.0.0) RNF v5 is complete rewrite with the aim of extensibility and smaller bundle size. Here are following changes on v5. Most of them are breaking change, but would take minimal effort from migrating from v4 to v5. [See migration doc](https://s-yadav.github.io/react-number-format/docs/migration) ##### Changes - React number format is broken into smaller Modules, NumericFormat and Pattern Format, so only things you need are exposed. - RNF provides lower level hooks and component (useNumericFormat, usePatternFormat) to allow full customisation. Check [customisation doc](https://s-yadav.github.io/react-number-format/docs/customization). - customNumerals prop is removed in favour of outside customization, [example](https://s-yadav.github.io/react-number-format/docs/customization#custom-numeral-example) - isNumericString prop is renamed to valueIsNumericString. ### [`v4.9.4`](https://togithub.com/s-yadav/react-number-format/compare/v4.9.3...v4.9.4) [Compare Source](https://togithub.com/s-yadav/react-number-format/compare/v4.9.3...v4.9.4)Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.