You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refactor the exported types from the `astro` module. There should normally be no breaking changes, but if you relied on some previously deprecated types, these might now have been fully removed.
6
+
7
+
In most cases, updating your code to move away from previously deprecated APIs in previous versions of Astro should be enough to fix any issues.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -289,7 +289,7 @@ Server-side rendering (SSR) can be complicated. The Astro package (`packages/ast
289
289
290
290
-`components/`: Built-in components to use in your project (e.g. `import Code from 'astro/components/Code.astro'`)
291
291
-`src/`: Astro source
292
-
-`@types/`: TypeScript types. These are centralized to cut down on circular dependencies
292
+
-`types/`: TypeScript types. These are centralized to cut down on circular dependencies
293
293
-`cli/`: Code that powers the `astro` CLI command
294
294
-`core/`: Code that executes **in the top-level scope** (in Node). Within, you’ll find code that powers the `astro build` and `astro dev` commands, as well as top-level SSR code.
295
295
-`runtime/`: Code that executes **in different scopes** (i.e. not in a pure Node context). You’ll have to think about code differently here.
* The prefix for Astro-generated asset links if the build.assetsPrefix config option is set. This can be used to create asset links not handled by Astro.
0 commit comments