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
* feat: switch to Azure Functions v4
* remove function.json - it is not needed anymore
* rename function path to "sk_render" since v4 does not allow the path to start with "__"
See also: https://techcommunity.microsoft.com/t5/apps-on-azure-blog/azure-functions-version-4-of-the-node-js-programming-model-is-in/ba-p/3773541closes#159
* add @azure/functions to external esbuild options (if not already there)
* Port over changes from #179
* Fix one unit test and update docs / release notes
* fix test 'writes to custom api directory'
* convert external function to v4
* fix headers test - use fetch API
* Update comments and docs
---------
Co-authored-by: Geoff Rich <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,15 @@
1
1
# Changelog
2
2
3
+
## [Unreleased]
4
+
5
+
### Features
6
+
7
+
***Breaking:** switch to Azure Functions v4:
8
+
* the function path has changed from `/api/__render` to `/api/sk_render` (v4 does not allow routes starting with underscores)
9
+
* see also [Migrate to version 4 of the Node.js programming model for Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/functions-node-upgrade-v4) from the Azure docs
Copy file name to clipboardExpand all lines: README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -119,7 +119,7 @@ custom/
119
119
└── index.js
120
120
```
121
121
122
-
Also note that the adapter reserves the folder prefix `sk_render` and API route prefix `__render` for Azure functions generated by the adapter. So, if you use a custom API directory, you cannot have any other folder starting with `sk_render` or functions available at the `__render` route, since these will conflict with the adapter's Azure functions.
122
+
Also note that the adapter reserves the folder prefix `sk_render` and API route prefix `sk_render` for Azure functions generated by the adapter. So, if you use a custom API directory, you cannot have any other folder starting with `sk_render` or functions available at the `sk_render` route, since these will conflict with the adapter's Azure functions.
123
123
124
124
### staticDir
125
125
@@ -240,6 +240,10 @@ This is currently only available when running in production on SWA. In addition,
240
240
241
241
All server requests to your SvelteKit app are handled by an Azure function. This property contains that Azure function's [request context](https://learn.microsoft.com/en-us/azure/azure-functions/functions-reference-node#context-object).
242
242
243
+
### `user`
244
+
245
+
The `user` property of the Azure function's [HTTP request](https://learn.microsoft.com/en-us/azure/azure-functions/functions-reference-node?tabs=javascript%2Cwindows%2Cazure-cli&pivots=nodejs-model-v4#http-request).
246
+
243
247
## Monorepo support
244
248
245
249
If you're deploying your app from a monorepo, here's what you need to know.
0 commit comments