-
Notifications
You must be signed in to change notification settings - Fork 8
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
fix(deps): update dependency @compiled/react to v0.18.3 #192
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/compiled-react-0.x
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/ruedap/nekostagram/225K4aQfKjpbA26rshobvPNwsNi8 |
4c062d4
to
9ec1502
Compare
9ec1502
to
7620fe5
Compare
7620fe5
to
caa8224
Compare
caa8224
to
21b5809
Compare
21b5809
to
246ba0e
Compare
246ba0e
to
0dec83c
Compare
0dec83c
to
8f09e20
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
8f09e20
to
6fd8b42
Compare
6fd8b42
to
1b0b5a1
Compare
94655fd
to
faff421
Compare
faff421
to
1cbaee7
Compare
1cbaee7
to
4f8a9e5
Compare
4f8a9e5
to
1030335
Compare
1030335
to
cf9bd23
Compare
cf9bd23
to
c6d6504
Compare
c6d6504
to
8ee8b15
Compare
8ee8b15
to
f610c41
Compare
f610c41
to
9dbd168
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:
0.6.13
->0.18.3
Release Notes
atlassian-labs/compiled (@compiled/react)
v0.18.3
Compare Source
Patch Changes
baa173c
: Fix type definition for CSS properties with string values.v0.18.2
Compare Source
Patch Changes
162210d
: Improve the types to thekeyframes()
function to handle CSS variables.v0.18.1
Compare Source
Patch Changes
1d2054c
: Protect @compiled/react/dist/browser/runtime in environments without a document defined.v0.18.0
Compare Source
Minor Changes
9a15e74
: Sort shorthand properties so that they come before longhand properties.When using Compiled, one of the following will happen:
Option 1. If stylesheet extraction is turned off ("runtime mode"): shorthand properties will be sorted before longhand properties, as long as they are not in a pseudo-selector like
:hover
or:active
. This is enabled by default and cannot be turned off.Option 2. If stylesheet extraction is turned on and one of the below is true:
... shorthand properties will only be sorted if
sortShorthand: true
is passed toCompiledExtractPlugin
(Webpack), orsortShorthand: true
is passed to your Compiled config file like.compiledcssrc
(Parcel). When sorting shorthand properties using this method (option 2), shorthand properties will always be sorted before longhand properties, taking precedence over pseudo-selectors like:hover
or:active
.v0.17.3
Compare Source
Patch Changes
25a4bed
: Fix thecx()
function's class collection at runtime as it generated class instances rather than stringsv0.17.2
Compare Source
Patch Changes
d75b828
: AddElementType
to the global compiled JSX namespacev0.17.1
Compare Source
Patch Changes
10c9dce
: added additional type exports to support other ts moduleResolution methodsv0.17.0
Compare Source
Minor Changes
39d9a02
: TherequiredPseudos
type property in XCSS prop has been removed.5701b91
: Types forcreateStrictAPI
have been refactored to improve type inference and expectations.Previously defining the schema came with a lot of redundant work. For every pseudo that you wanted to type you would have to define it, and then all of the base types again, like so:
If you missed a value / didn't type every possible pseudo it would fallback to the CSSProperties value from csstype. This was mostly unexpected. So for example right now
&:hover
has been typed, but no other pseudo... meaning no other pseudos would benefit from the schema types!With this refactor all CSS properties use the top types unless a more specific one is defined, meaning you only need to type the values you want to explicitly support. In the previous example we're now able to remove the
background
property as it's the same as the top one.interface Schema { background: 'var(--bg)'; color: 'var(--color)'; '&:hover': { - background: 'var(--bg)'; color: 'var(--color-hovered)'; }; } createStrictAPI<Schema>();
Patch Changes
4b2e5ee
: - The CSS map API now allows defining top level media queries. Previously you had to define them inside a@media
object, this restriction has now been removed bringing it inline with the CSS function API.XCSS prop
The XCSS prop now takes top level media queries. Nested media queries is not allowed.
createStrictAPI
Now takes an optional second generic to define what media queries are supported:
createStrictAPI< { color: 'var(--text)' } + { media: '(min-width: 30rem)' | '(min-width: 48rem)' } >();
Which is then flushed to all output APIs.
20528e9
: Better cssMap types: fix inference of complex types and adds descriptions to the type.v0.16.10
Compare Source
Patch Changes
a68817a
: Fix css function base types to have CSS property values available in intellisense.v0.16.9
Compare Source
Patch Changes
541ab19
: AddElementType
to the Compiled JSX namespace. This is needed to ensure types are the same in the Compiled JSX namspace and the default React one, such as returningundefined
,string
, and other freshly valid types.v0.16.8
Compare Source
Patch Changes
39714ae
: Fix nested types being forcibly required.v0.16.7
Compare Source
Patch Changes
5dca5c5
: ExportCSSPseudos, CSSProperties, StrictCSSProperties
types for a strictXCSSProp
implementation.v0.16.6
Compare Source
Patch Changes
34674ae
: FixcssMap
returned fromcreateStrictAPI
to return types based on the generic input, fixing usage with theXCSSProp
API.v0.16.5
Compare Source
Patch Changes
cd11b42
: Block invalid properties on ourcssMap
input objects to avoid invalid css and other mistakes.v0.16.4
Compare Source
Patch Changes
e9b50b4
: Add custom error message to be shown when any output from createStrictAPI() is unexpectedly executed.v0.16.3
Compare Source
Patch Changes
9857009
: Introduce new APIcreateStrictAPI
which returns a strict subset of Compiled APIs augmented by a type definition.This API does not change Compileds build time behavior — merely augmenting
the returned API types which enforce:
To set up:
// .compiledcssrc { + "importSources": ["./foo.ts"] }
v0.16.2
Compare Source
Patch Changes
be019f1
: Add detectConflictWithOtherLibraries and onlyRunIfImportingCompiled config options to jsx-pragma ESLint rule. Both are set to true by default, hence the breaking change.detectConflictWithOtherLibraries
raises a linting error ifcss
orjsx
is imported from@emotion/react
(or@emotion/core
) in the same fileas a Compiled import. Set to true by default.
onlyRunIfImportingCompiled
sets this rule to only suggest adding the JSX pragma if thecss
orcssMap
functions are imported from@compiled/react
, as opposed to whenever thecss
attribute is detected at all. Set to false by default.v0.16.1
Compare Source
Patch Changes
a68817a
: Fix css function base types to have CSS property values available in intellisense.v0.16.0
Compare Source
Minor Changes
f8d01fa
: Remove Flow types as they are increasingly difficult to maintainv0.15.0
Compare Source
Minor Changes
b6f3e41
: ChangecssMap
types to use stricter type checking and only allowing a limited subset of whitelisted selectors (e.g.&:hover
); implement syntax for at-rules (e.g.@media
); implementselectors
key for non-whitelisted selectors.v0.14.0
Compare Source
Minor Changes
4a2174c
: Implement thecssMap
API to enable library users to dynamically choose a varied set of CSS rules.Patch Changes
c5377cd
: Ensure that the return types ofcss
andcssMap
are readonly.v0.13.1
Compare Source
Patch Changes
cd97765
: Remove@compiled/react
runtime side-effect to ensure no error if the module is reloaded.v0.13.0
Compare Source
Minor Changes
c4e6b7c
: Introduce a new runtime class name library, which resolves theax
chaining issue. The new library is used only if class name compression is enabled.c4e6b7c
: Change TypeScript compiler target from es5 to es6.v0.12.0
Compare Source
Minor Changes
a41e41e
: Update monorepo node version to v18, and drop support for node v12f9c957e
: Add an option to compress class names based on "classNameCompressionMap", which is provided by library consumers.Add a script to generate compressed class names.
v0.11.4
Compare Source
Patch Changes
6df1976
: Update isServerEnvironment to support different SSR environmentv0.11.3
Compare Source
Patch Changes
acd8996
: Fix react runtime ax function returning incorrect result for selectorsv0.11.2
Compare Source
Patch Changes
08a963f
: Bump flowgen typesv0.11.1
Compare Source
Patch Changes
13b71df
: - Give a name to CSS var used for empty valuesv0.11.0
Compare Source
Minor Changes
1cab89a
: check node environment based onprocess
instead ofwindow
Patch Changes
ad4d257
: Update TypeScript and Flow types to support function calls and resolve incorrect typingv0.10.4
Compare Source
Patch Changes
356b120
: Apply react/jsx-filename-extension rule as neededv0.10.3
Compare Source
Patch Changes
47050f4
: Add client CS benchmarkv0.10.2
Compare Source
Patch Changes
254a6f6
: Added ESLint rule to prevent use of extraneous packages, and added these usages of these packages as dependencies. Added new namespace@compiled-private
to prevent name clashes with existing npm packages.c757259
: Update type definition dependencies6649528
: Changed the SSR check to be based on the presence ofdocument
instead of looking for Node processes.v0.10.1
Compare Source
Patch Changes
d3e257c
: Fixescss
function types to allow nested styles8c9ab8c
: Updatehomepage
and otherpackage.json
properties8c9ab8c
: JSDoc descriptions for all exports have been updated, let us know what you think!8c9ab8c
:ClassNames
component now has its style prop typed asCSSProperties
instead of a string mapv0.10.0
Compare Source
Minor Changes
427cead
: Breaking change: When using thecss
prop with TypeScript you now need to declare a JSX pragma enabling types for that module. Previously when importing the@compiled/react
package the global JSX namespace would be polluted as a side effect potentially causing collisions with other CSS-in-JS libraries. Now thanks to the use of locally scoped JSX namespaces the global JSX namespace will no longer be polluted.As an added bonus the
css
prop will only be available on JSX elements that have also defined aclassName
prop with the potential for more type safe features later on.Make sure to update all Compiled dependencies to latest when adopting this change.
Automatic runtime
Classic runtime
To aid consumers in adopting this change easily, a new ESLint rule
jsx-pragma
has been created which will automatically migrate you to use a JSX pragma if missing when running with--fix
. The rule takes an option to configure the runtime (either classic or automatic) and defaults to automatic.Patch Changes
79cfb08
: Internal refactor changing how the TypeScript compiler picks up source files.v0.9.1
Compare Source
Patch Changes
4309aaa
: Patch inexact flow type on styledv0.9.0
Compare Source
Minor Changes
2092839
: Allow inline strings and inline css mixins in conditional expressions. Fix ordering of styles in template literals.v0.8.0
Compare Source
Minor Changes
4210ff6
: Add flow types support53935b3
: AddObjectExpression
support tocss
v0.7.0
Compare Source
Minor Changes
bcb2a68
: Add support forkeyframes
a7ab8e1
: Add support for conditional rules forStyled
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone Asia/Tokyo, 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 was generated by Mend Renovate. View the repository job log.