-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update all dependencies (major) (major) #25
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-all-dependencies-(major)
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/khushrajrathod/tic-tac-toe/AAMnHbRyiYJ1Q8pAjBVEHPgaPpxK |
a63cbd9
to
67b0eb1
Compare
67b0eb1
to
917bb93
Compare
917bb93
to
edd0e38
Compare
edd0e38
to
f103309
Compare
f103309
to
525bf4c
Compare
525bf4c
to
7b44fad
Compare
7b44fad
to
2996afc
Compare
2996afc
to
908a706
Compare
908a706
to
df2fa22
Compare
df2fa22
to
4a94bf9
Compare
4a94bf9
to
0269d70
Compare
0269d70
to
666944e
Compare
666944e
to
0c8173c
Compare
0c8173c
to
142fd81
Compare
142fd81
to
8b6fb0f
Compare
8b6fb0f
to
9671102
Compare
9671102
to
06d347a
Compare
06d347a
to
1376ab4
Compare
1376ab4
to
722f3a7
Compare
722f3a7
to
0bb3e7a
Compare
0bb3e7a
to
6b3d49e
Compare
6b3d49e
to
7742c7b
Compare
7742c7b
to
ad60e9e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^11.1.0
->12.0.0
^12.1.10
->13.2.1
^26.0.23
->27.0.1
^9
->10.3.4
^7
->8.3.6
^1.0.1
->2.1.0
Release Notes
testing-library/react-testing-library
v12.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
@testing-library/dom
to 8.0.0. Please check out the@testing-library/dom@8.0.0
release page for a detailed list of breaking changes.testing-library/user-event
v13.2.1
Compare Source
Bug Fixes
v13.2.0
Compare Source
Features
ArrowLeft
andArrowRight
on<textarea>
(#686) (f8f00d4)v13.1.9
Compare Source
Bug Fixes
<input>
(#679) (f2fec13)v13.1.8
Compare Source
Bug Fixes
v13.1.7
Compare Source
Bug Fixes
v13.1.6
Compare Source
Bug Fixes
v13.1.5
Compare Source
Bug Fixes
v13.1.4
Compare Source
Bug Fixes
checkbox
/radio
as clickable inputs (#654) (35d996e)v13.1.3
Compare Source
Bug Fixes
click
/hover
onpointer-events: none
(#647) (6b2ce66)v13.1.2
Compare Source
Bug Fixes
global.document
(#642) (c69a74a)v13.1.1
Compare Source
Bug Fixes
v13.1.0
Compare Source
Features
v13.0.16
Compare Source
Bug Fixes
<input type="number">
(#628) (f633a52)v13.0.15
Compare Source
Bug Fixes
v13.0.14
Compare Source
Bug Fixes
v13.0.13
Compare Source
Bug Fixes
v13.0.12
Compare Source
Bug Fixes
v13.0.11
Compare Source
Bug Fixes
v13.0.10
Compare Source
Bug Fixes
v13.0.9
Compare Source
Bug Fixes
v13.0.8
Compare Source
Bug Fixes
v13.0.7
Compare Source
Bug Fixes
v13.0.6
Compare Source
Bug Fixes
v13.0.5
Compare Source
Bug Fixes
v13.0.4
Compare Source
Bug Fixes
v13.0.3
Compare Source
Bug Fixes
v13.0.2
Compare Source
Bug Fixes
v13.0.1
Compare Source
Bug Fixes
v13.0.0
Compare Source
Features
BREAKING CHANGES
userEvent.type
features a rewritten implementation shared with the newuserEvent.keyboard
. This might break code depending on unintended/undocumented behavior of the previous implementation.userEvent.type
treats{
and[
as special characters.userEvent.type
returns no Promise if called withoutdelay
.postcss/autoprefixer
v10.3.4
Compare Source
stretch
value in latest Firefox.v10.3.3
Compare Source
-moz-
prefix from::file-selector-button
(by Usman Yunusov).v10.3.2
Compare Source
::file-selector-button
support (by Usman Yunusov).v10.3.1
Compare Source
content
(by Luke Warlow).v10.3.0
Compare Source
In Autoprefixer 10.3 @lukewarlow added
::file-selector-button
support.v10.2.6
Compare Source
v10.2.5
Compare Source
:
support in@supports
(by Dmitry Semigradsky).v10.2.4
Compare Source
npx autoprefixer --info
.v10.2.3
Compare Source
v10.2.2
Compare Source
v10.2.1
Compare Source
transition-property
warnings (by @Sheraff).v10.2.0
Compare Source
Autoprefixer 10.2 now has built-in TypeScript definitions. You do not need
@types/autoprefixer
anymore.Thanks to @Semigradsky and DefinitelyTyped’s contributors.
@Sheraff also improved docs.
v10.1.0
Compare Source
Autoprefixer 10.1 improved
min-resolution
support.@infusion added
dpcm
unit support andnum2fraction
with Fraction.js, which uses Farey Sequences as a rational approximation (more precise) and simplifies the fraction using continued fractions to ɛ <0.001 afterward.v10.0.4
Compare Source
Cannot read property 'proxyOf' of undefined
error (by Igor Kamyshev).v10.0.3
Compare Source
substract
tosubtract
value formask-composite
(by Michelle Enos).v10.0.2
Compare Source
-ms-user-select: all
because IE and old Edge don’t support it.v10.0.1
Compare Source
package.json
.v10.0.0
Compare Source
Autoprefixer 10 is based on top of PostCSS 8 (check Known Issues section before updating).
Node.js 6.x, 8.x, 11.x support was removed.
Now you need to install Autoprefixer by
npm install --save-dev autoprefixer postcss
. We movedpostcss
fromdependencies
topeerDependencies
according to new PostCSS plugin guidelines.postcss/postcss
v8.3.6
Compare Source
missed semicolon
error (by @Gusted).v8.3.5
Compare Source
v8.3.4
Compare Source
v8.3.3
Compare Source
postcss
dependency duplication in custom parsers.v8.3.2
Compare Source
v8.3.1
Compare Source
PostCSS does nothing
warning onsyntax
option.v8.3.0
Compare Source
PostCSS 8.3 improved source map parsing performance, added
Node#assign()
shortcut, and experimentalDocument
node to AST.Thanks to Sponsors
This release was possible thanks to our community.
If your company wants to support the sustainability of front-end infrastructure or wants to give some love to PostCSS, you can join our supporters by:
Source Map Performance
Because PostCSS needs synchronous API, we can’t move from the old `source-map 0.6 to 0.7 (many other open-source projects too).
@7rulnik forked
source-map
0.6 tosource-map-js
and back-ported performance improvements from 0.7. In 8.3 we switched fromsource-map
to thissource-map-js
fork.You map see 4x performance improvements in parsing map from processing step before PostCSS (for instance, Sass).
Document
NodesThanks to @gucong3000, PostCSS already parse CSS from HTML and JS files (CSS-in-JS templates and objects).
But his plugin need big updates. @hudochenkov from stylelint team decided to create new parsers for styles inside CSS-in-JS, HTML, and Markdown.
He suggested adding new
Document
node type to PostCSS AST to keep multipleRoot
nodes inside and JS/HTML/Markdown code blocks between these style blocks.This is an experimental feature. Some aspects of this node could change within minor or patch version releases.
Node#assign()
ShortcutThe creator of famous
postcss-preset-env
and many other PostCSS tools, @jonathantneal suggested a nice shortcut to change multiple properties in the node:v8.2.15
Compare Source
list
type definitions (by @n19htz).v8.2.14
Compare Source
source-map
from client-side bundle (by Barak Igal).v8.2.13
Compare Source
v8.2.12
Compare Source
package.json
exports.v8.2.11
Compare Source
DEP0148
warning in Node.js 16.v8.2.10
Compare Source
v8.2.9
Compare Source
NodeErrorOptions
type (by Rouven Weßling).v8.2.8
Compare Source
v8.2.7
Compare Source
v8.2.6
Compare Source
v8.2.5
Compare Source
list.split
(by Natalie Weizenbaum).v8.2.4
Compare Source
postcss.plugin()
warning (by Tom Williams).v8.2.3
Compare Source
JSON.stringify(Node[])
support (by Niklas Mischkulnig).v8.2.2
Compare Source
Result#warn()
types.v8.2.1
Compare Source
list
type definitions (by @n19htz).v8.2.0
Compare Source
PostCSS 8.2 added a new API to serialize and deserialize CSS AST to JSON.
Thanks to @mischnic for his work.
v8.1.14
Compare Source
v8.1.13
Compare Source
v8.1.12
Compare Source
v8.1.11
Compare Source
v8.1.10
Compare Source
LazyResult
type export (by Evan You).LazyResult
type compatibility withPromise
(by Anton Kastritskiy).v8.1.9
Compare Source
v8.1.8
Compare Source
LazyResult
type compatibility withPromise
(by Ludovico Fischer).v8.1.7
Compare Source
import
support in TypeScript (by Remco Haszing).v8.1.6
Compare Source
package.exports
Node.js 15 fix.v8.1.5
Compare Source
v8.1.4
Compare Source
v8.1.3
Compare Source
package.types
.v8.1.2
Compare Source
v8.1.1
Compare Source
v8.1.0
Compare Source
PostCSS 8.1 fixed the new visitor API from the 8.0 release.
We fixed
Root
andRootExit
re-calling on children's changes. And now visitors will visit the parent again if nested children were changed.We added
Once
andOnceExit
events, which will not be called again on node changes. You can use them to lint files or collect statistics:We updated Migration guide according to new changes.
v8.0.9
Compare Source
Transformer
to exported types (by Pierre-Marie Dartus).v8.0.8
Compare Source
8.0.7
regression on PostCSS 7 nodes converting (by Adam Wathan).v8.0.7
Compare Source
v8.0.6
Compare Source
Container
.v8.0.5
Compare Source
v8.0.4
Compare Source
Cannot read property 'line' of null
error.v8.0.3
Compare Source
v8.0.2
Compare Source
v8.0.1
Compare Source
Processor#version
.v8.0.0
Compare Source
PostCSS 8.0 brings new plugin API,
node_modules
size reduction, better source map support, and CSS parser improvements.Check out a day-by-day diary of PostCSS 8.0 development process.
See Migration Guides for end-users and for plugin developers.
Thanks to Sponsors
With more than 100 M downloads per month, it becomes hard to support PostCSS in free time. For instance, getting the 8.0 release ready took 4 months of work.
This release was possible thanks to out community. Tailwind CSS, De Voorhoede, InVision AG, Brainbow, and many individual contributions.
If your company wants to support the sustainability of front-end infrastructure or just wants to give some love to PostCSS, you can join our supporters by:
Breaking Changes
We try to avoid any breaking changes for end-users:
node_modules/postcss
for old browsers.postcss.vendor
API.New Plugin API
The biggest change in PostCSS 8 is a new plugin API. Thanks to @BondarenkoAlex for big help in creating a new API.
We know that rewriting old plugins will take time, but the new API will improve the end-user’s experience and make life easier for plugin developers:
postcss
duplicates in yournode_modules
. New API fixes this problem.These resources will help plugin developers in API migration:
PostCSS development guidelines were also changed:
postcss
inpeerDependencies
.New Website without React
Previously PostCSS used a React-based framework for the project's website. Since we have a static website, we decided to migrate to a React-free framework and got good performance improvements:
Check out postcss.org and new API docs that feature the awesome alchemy-inspired design by @okonet.
We also removed Google Analytics tracking scripts and encourage other open source projects to be an example in caring about user’s privacy and performance.
Parser Improvments
Did you know that all examples below are valid CSS?
Now PostCSS parses even those rare edge cases correctly. Thanks to Tailwind CSS and Prettier teams for adding more cases to our CSS parser tests collection.
Note that now
--roundMixin: { border-radius: 8px }
will be parsed as aDeclaration
with the{ border-radius: 8px }
value.Better Source Map Support
We have added support for two new source map formats: Index map and JSON (
data:application/json
).PostCSS 8 is now much closer to the source map spec. Thanks to the Google team for reports:
sources
in map as URLs instead of file paths.sources
relative to map file, not CSS file.A few source map APIs were added:
opts.maps.absolute = true
option for absolute paths in source map.opts.maps.annotation = (file, root) => url
for a dynamic path to source map.Node#origin()
now returnsposition.url
in addition toposition.file
for compatibility with absolute URLs in source map’ssources
.API Changes
We have added ES modules support and now we export all classes from the main entry:
@graberzz added
Node#source.offset
in addition toline
andcolumn
.CSS Custom Properties and Sass-like
$
-variables now have a specialDeclaration#variable
mark:TypeScript
PostCSS now has a first-class TypeScript support:
Other Changes
replaceWith
with input replaced node (by @josephkaptur).chalk
tocolorette
.Declaration#value
auto-conversion to string to prevent plugin’s bugs.<input css 9M4X8l>:10:6
.GoogleChrome/web-vitals
v2.1.0
Compare Source
v2.0.1
Compare Source
v2.0.0
Compare Source
Configuration
📅 Schedule: "after 1:00am and before 9:00am" in timezone Asia/Kolkata.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by WhiteSource Renovate. View repository job log here.