@react-email/tailwind 1.0.3-canary.0 → 1.0.3-canary.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +11 -11
- package/readme.md +4 -3
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@react-email/tailwind",
|
|
3
|
-
"version": "1.0.3-canary.
|
|
3
|
+
"version": "1.0.3-canary.1",
|
|
4
4
|
"description": "A React component to wrap emails with Tailwind CSS",
|
|
5
5
|
"sideEffects": false,
|
|
6
6
|
"main": "./dist/index.js",
|
|
@@ -35,7 +35,7 @@
|
|
|
35
35
|
"engines": {
|
|
36
36
|
"node": ">=18.0.0"
|
|
37
37
|
},
|
|
38
|
-
"
|
|
38
|
+
"peerDependencies": {
|
|
39
39
|
"react": "^18.0 || ^19.0 || ^19.0.0-rc"
|
|
40
40
|
},
|
|
41
41
|
"devDependencies": {
|
|
@@ -54,15 +54,15 @@
|
|
|
54
54
|
"vite-plugin-dts": "4.2.4",
|
|
55
55
|
"vitest": "1.1.1",
|
|
56
56
|
"yalc": "1.0.0-pre.53",
|
|
57
|
-
"@react-email/button": "^0.0.19-canary.
|
|
58
|
-
"@react-email/
|
|
59
|
-
"@react-email/
|
|
60
|
-
"@react-email/
|
|
61
|
-
"@react-email/
|
|
62
|
-
"@react-email/
|
|
63
|
-
"@react-email/
|
|
64
|
-
"
|
|
65
|
-
"
|
|
57
|
+
"@react-email/button": "^0.0.19-canary.1",
|
|
58
|
+
"@react-email/hr": "0.0.11-canary.1",
|
|
59
|
+
"@react-email/html": "0.0.11-canary.1",
|
|
60
|
+
"@react-email/link": "0.0.12-canary.1",
|
|
61
|
+
"@react-email/head": "0.0.12-canary.1",
|
|
62
|
+
"@react-email/heading": "0.0.15-canary.1",
|
|
63
|
+
"@react-email/render": "1.0.3-canary.3",
|
|
64
|
+
"eslint-config-custom": "0.0.0",
|
|
65
|
+
"tsconfig": "0.0.0"
|
|
66
66
|
},
|
|
67
67
|
"publishConfig": {
|
|
68
68
|
"access": "public"
|
package/readme.md
CHANGED
|
@@ -77,9 +77,10 @@ and the class names associated with them on a `<style>` tag on the `<head>` elem
|
|
|
77
77
|
|
|
78
78
|
### The treatment for Tailwind's CSS variables
|
|
79
79
|
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
80
|
+
Emails don't really have great support for CSS variables,
|
|
81
|
+
so we needed to use a custom postcss plugin alongisde Tailwind to resolve
|
|
82
|
+
all of these variables. When the plugin finds a CSS Variable that it cannot resolve,
|
|
83
|
+
it leaves it without any changes.
|
|
83
84
|
|
|
84
85
|
### The treatment for media query class names
|
|
85
86
|
|