File tree 3 files changed +8
-0
lines changed
build-output-api/serverless-functions
3 files changed +8
-0
lines changed Original file line number Diff line number Diff line change
1
+ index.func
Original file line number Diff line number Diff line change @@ -6,6 +6,7 @@ module.exports = (req, res) => {
6
6
const text =
7
7
`Howdy ${ name } , from Vercel!\n` +
8
8
`Node.js: ${ process . version } \n` +
9
+ `Request URL: ${ req . url } \n` +
9
10
`Server time: ${ new Date ( ) . toISOString ( ) } )`
10
11
const body = cowsay . say ( { text } )
11
12
Original file line number Diff line number Diff line change @@ -23,3 +23,9 @@ source code file will be the starting point of execution when the Serverless Fun
23
23
Additional files may placed within the ` index.func ` file as well which will be included in the runtime environment
24
24
of the Serverless Function. In this case, there is also a ` node_modules ` directory
25
25
that contains dependencies that the example Serverless Function needs in order to operate.
26
+
27
+ A second Serverless Function is also included at the path
28
+ ` .vercel/output/functions/another.func ` . In this case, it is represented by using
29
+ a symbolic link that points to the ` index.func ` directory. Because it is a
30
+ symlink, Vercel will optimize this by only creating one backing Serverless
31
+ Function which is served at both URL paths.
You can’t perform that action at this time.
0 commit comments