UNPKG

8.77 kBMarkdownView Raw
1# microsite
2
3## 0.6.5
4
5### Patch Changes
6
7- f65c7f4: Improve types by adding global `h` and `Fragment`, and ambient `*.modules.css` declarations
8
9## 0.6.4
10
11### Patch Changes
12
13- e53864f: Update default `tsconfig` to be named `base`.
14
15 Update `tsconfig.baseUrl` to resolve from inside `node_modules`
16
17## 0.6.3
18
19### Patch Changes
20
21- a760228: Automatically inject h and Fragment
22- 580bb4f: expose default tsconfig.json for end-users
23
24## 0.6.2
25
26### Patch Changes
27
28- 60de6a2: Fix esbuild jsxFactory
29
30## 0.6.1
31
32### Patch Changes
33
34- a3a5131: Fix external warning
35- 5c79ec3: update README
36
37## 0.6.0
38
39### Breaking Changes
40
41- 9d0e9cc: Drop `@types/react` and switch to `preact`. See issue [#5](https://github.com/natemoo-re/microsite/issues/5) for more background.
42
43## 0.0.0-canary-2020101419274
44
45### Breaking Changes
46
47- 7fd4679: Drop `@types/react` and switch to `preact`. See issue [#5](https://github.com/natemoo-re/microsite/issues/5) for more background.
48
49## 0.5.1
50
51### Patch Changes
52
53- 3d99331: Fix handling of node builtins for intermediate builds
54- 3d99331: Remove .microsite/cache dir for now
55
56## 0.5.1-next.0
57
58### Patch Changes
59
60- a29b71e: Fix handling of node builtins for intermediate builds
61- 078b910: Remove .microsite/cache dir for now
62
63## 0.5.0
64
65### Minor Changes
66
67- 47eec22: **Build performance improvements**
68
69 Rather than relying on [`@rollup/plugin-typescript`](https://github.com/rollup/plugins/tree/master/packages/typescript) (which uses `typescript` under the hood), we have switched to [`rollup-plugin-esbuild`](https://github.com/egoist/rollup-plugin-esbuild) to perform code transforms.
70
71 [`esbuild`](https://github.com/evanw/esbuild) is very very fast. Now, so is Microsite.
72
73### Patch Changes
74
75- 275f297: Gracefully handle Component/export name mismatch
76
77 Automatically handle `tsconfig.paths` aliases
78
79- 945685d: **SEO**
80
81 Microsite aims to make SEO as simple as possible, so this featureset adds built-in SEO utility components to `microsite/head` under the `seo` namespace.
82
83 The benefit of using `seo` components over manual `meta` tag configuration is API simplicity, since `seo` automatically configures duplicate [Open Graph](https://ogp.me/)/social meta tags for you.
84
85 If something here doesn't cover your use case, please feel free to [open an issue](https://github.com/natemoo-re/microsite/issues/new).
86
87 ```tsx
88 import { Head, seo } from "microsite/head";
89
90 <Head>
91 <seo.title>Easy SEO</seo.title>
92 <seo.description>Hello world!</seo.description>
93 <seo.image
94 src="https://og-image.now.sh/**Hello**%20World.png?theme=light&md=1&fontSize=100px&images=https%3A%2F%2Fassets.vercel.com%2Fimage%2Fupload%2Ffront%2Fassets%2Fdesign%2Fvercel-triangle-black.svg"
95 width={100}
96 height={100}
97 />
98 <seo.twitter handle="@n_moore" />
99 </Head>;
100 ```
101
102 #### seo.robots
103
104 By default, `<Head>` now automatically adds the following tags.
105
106 ```html
107 <meta name="robots" content="index,follow" />
108 <meta name="googlebot" content="index,follow" />
109 ```
110
111 This behavior can be controlled with the `<seo.robots>` helper, which accepts `noindex` and `nofollow` booleans.
112
113 ```tsx
114 <seo.robots noindex nofollow />
115 ```
116
117 #### seo.title
118
119 `<seo.title>` has the same API as a regular `<title>` tag—it accepts a `string` child. `<seo.title>` sets the page `<title>` as well as `<meta property="og:title">`.
120
121 #### seo.description
122
123 `<seo.description>` accepts a `string` child. `<seo.description>` sets `<meta name="description">` as well as `<meta property="og:description">`.
124
125 #### seo.canonical
126
127 `<seo.canonical>` accepts a `string` child representing the canonical URL of the current page. It generates `<link rel="canonical">` and `<meta property="og:url">`.
128
129 #### seo.image
130
131 `<seo.image>` exposes an API similar to the native `<img>`, accepting `src`, `alt`, `width`, and `height` props. It generates all the meta tags necessary for valid Open Graph images.
132
133 #### seo.video
134
135 `<seo.video>` exposes an API similar to the native `<video>`, accepting `src`, `width`, and `height` props. It generates all the meta tags necessary for valid Open Graph videos.
136
137 #### seo.audio
138
139 `<seo.audio>` exposes an API similar to the native `<audio>`, accepting only a `src` prop. It generates all the meta tags necessary for valid Open Graph audio.
140
141 #### seo.twitter
142
143 `<seo.twitter>` controls [Twitter meta tags](https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/markup). It accepts `card`, `handle` (maps to `twitter:creator`), and `site`.
144
145 #### seo.facebook
146
147 `<seo.facebook>` accepts an `appId` in order to set `<meta property="fb:app_id">`.
148
149 #### seo.openGraph
150
151 `<seo.openGraph>` provides low-level control over [Open Graph meta tags](https://ogp.me/). The accepted props vary based on `type`, so you might want to dig [into the code](https://github.com/natemoo-re/microsite/blob/8c0599f8c05da3214534b864c536a2614a89fb7f/src/head.tsx#L14) for this one.
152
153- 17e3130: Fix issue when building projects without optional global/hydrated files
154- da6e0f3: Improve build performance (parallelization)
155- eaec00b: Fixes issue with static path generation for the `/` route
156
157## 0.5.0-alpha.0
158
159### Minor Changes
160
161- 47eec22: **Build performance improvements**
162
163 Rather than relying on [`@rollup/plugin-typescript`](https://github.com/rollup/plugins/tree/master/packages/typescript) (which uses `typescript` under the hood), we have switched to [`rollup-plugin-esbuild`](https://github.com/egoist/rollup-plugin-esbuild) to perform code transforms.
164
165 [`esbuild`](https://github.com/evanw/esbuild) is very very fast. Now, so is Microsite.
166
167### Patch Changes
168
169- 945685d: **SEO**
170
171 Microsite aims to make SEO as simple as possible, so this featureset adds built-in SEO utility components to `microsite/head` under the `seo` namespace.
172
173 The benefit of using `seo` components over manual `meta` tag configuration is API simplicity, since `seo` automatically configures duplicate [Open Graph](https://ogp.me/)/social meta tags for you.
174
175 If something here doesn't cover your use case, please feel free to [open an issue](https://github.com/natemoo-re/microsite/issues/new).
176
177 ```tsx
178 import { Head, seo } from "microsite/head";
179
180 <Head>
181 <seo.title>Easy SEO</seo.title>
182 <seo.description>Hello world!</seo.description>
183 <seo.image
184 src="https://og-image.now.sh/**Hello**%20World.png?theme=light&md=1&fontSize=100px&images=https%3A%2F%2Fassets.vercel.com%2Fimage%2Fupload%2Ffront%2Fassets%2Fdesign%2Fvercel-triangle-black.svg"
185 width={100}
186 height={100}
187 />
188 <seo.twitter handle="@n_moore" />
189 </Head>;
190 ```
191
192 #### seo.robots
193
194 By default, `<Head>` now automatically adds the following tags.
195
196 ```html
197 <meta name="robots" content="index,follow" />
198 <meta name="googlebot" content="index,follow" />
199 ```
200
201 This behavior can be controlled with the `<seo.robots>` helper, which accepts `noindex` and `nofollow` booleans.
202
203 ```tsx
204 <seo.robots noindex nofollow />
205 ```
206
207 #### seo.title
208
209 `<seo.title>` has the same API as a regular `<title>` tag—it accepts a `string` child. `<seo.title>` sets the page `<title>` as well as `<meta property="og:title">`.
210
211 #### seo.description
212
213 `<seo.description>` accepts a `string` child. `<seo.description>` sets `<meta name="description">` as well as `<meta property="og:description">`.
214
215 #### seo.canonical
216
217 `<seo.canonical>` accepts a `string` child representing the canonical URL of the current page. It generates `<link rel="canonical">` and `<meta property="og:url">`.
218
219 #### seo.image
220
221 `<seo.image>` exposes an API similar to the native `<img>`, accepting `src`, `alt`, `width`, and `height` props. It generates all the meta tags necessary for valid Open Graph images.
222
223 #### seo.video
224
225 `<seo.video>` exposes an API similar to the native `<video>`, accepting `src`, `width`, and `height` props. It generates all the meta tags necessary for valid Open Graph videos.
226
227 #### seo.audio
228
229 `<seo.audio>` exposes an API similar to the native `<audio>`, accepting only a `src` prop. It generates all the meta tags necessary for valid Open Graph audio.
230
231 #### seo.twitter
232
233 `<seo.twitter>` controls [Twitter meta tags](https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/markup). It accepts `card`, `handle` (maps to `twitter:creator`), and `site`.
234
235 #### seo.facebook
236
237 `<seo.facebook>` accepts an `appId` in order to set `<meta property="fb:app_id">`.
238
239 #### seo.openGraph
240
241 `<seo.openGraph>` provides low-level control over [Open Graph meta tags](https://ogp.me/). The accepted props vary based on `type`, so you might want to dig [into the code](https://github.com/natemoo-re/microsite/blob/8c0599f8c05da3214534b864c536a2614a89fb7f/src/head.tsx#L14) for this one.
242
\No newline at end of file