# Display Node.js and Twilio SDK versions

Sometimes, such as when you are [migrating to the latest version of Node.js](/docs/serverless/functions-assets/node-upgrade), you want to verify what version of Node.js your Functions are running on. The same can apply to the version of the [Twilio Node.js SDK](https://github.com/twilio/twilio-node) that you are using, since its version determines what functionality is available via the [context.getTwilioClient](/docs/serverless/functions-assets/functions/invocation#helper-methods) helper.

The following code sample shows some helpful values that you can return or log for verification. To get started, follow the instructions below to create a Service and Function to host and execute the example.

## Create and host a Function

Before you run any of the examples on this page, create a Function and paste the example code into it. You can create a Function in the Twilio Console or by using the [Serverless Toolkit](/docs/labs/serverless-toolkit).

## Console

If you prefer a UI-driven approach, complete these steps in the Twilio Console:

1. Log in to the [Twilio Console](https://1console.twilio.com) and navigate to **Develop > Functions & Assets**. If you're using the *legacy* Console, open the [**Functions** tab](https://www.twilio.com/console/functions/overview).
2. Functions are contained within **Services**. Click **[Create Service](https://www.twilio.com/console/functions/overview/services)** to create a new **[Service](/docs/serverless/functions-assets/functions/create-service)**.
3. Click **Add +** and select **Add Function** from the dropdown.
4. The Console creates a new [protected](/docs/serverless/functions-assets/visibility) Function that you can rename. The filename becomes the URL path of the Function.
5. Copy one of the example code snippets from this page and paste the code into your newly created Function. You can switch examples by using the dropdown menu in the code rail.
6. Click **Save**.
7. Click **Deploy All** to build and deploy the Function. After deployment, you can access your Function at `https://<service-name>-<random-characters>-<optional-domain-suffix>.twil.io/<function-path>`\
   For example: `test-function-3548.twil.io/hello-world`.

## Serverless Toolkit

The [Serverless Toolkit](/docs/labs/serverless-toolkit) lets you develop locally, deploy projects, and perform other tasks through the [Twilio CLI](/docs/twilio-cli/quickstart).

1. From the CLI, run `twilio serverless:init <YOUR-SERVICE-NAME> --empty` to bootstrap your local environment.
2. Go to your new project directory using `cd <YOUR-SERVICE-NAME>`.
3. In the `/functions` directory, create a JavaScript file whose name reflects the purpose of the Function. For example, `sms-reply.protected.js` for a [protected](/docs/serverless/functions-assets/visibility) Function intended to handle incoming SMS.
4. Add the code example of your choice to the file and save it. Note that a Function can only export a single handler. You need to create separate files to run or deploy multiple examples at once.

After you save the Function code, you can test it locally (and optionally tunnel requests to it using a tool like [ngrok](https://ngrok.com/)), or deploy it.

### Run your Function in local development

Run `twilio serverless:start` from your CLI to start the project locally. The Function(s) in your project are accessible from `http://localhost:3000/sms-reply`

* If you want to test a Function as a [Twilio webhook](/docs/usage/webhooks/getting-started-twilio-webhooks), run: `twilio phone-numbers:update <your Twilio phone number> --sms-url "http://localhost:3000/sms-reply"`\
  This automatically generates an ngrok tunnel from Twilio to your locally running Function, so you can start sending texts to it. You can apply the same process but with the `voice-url` flag instead to test with [Twilio Voice](/docs/voice).
* If your code does *not* connect to Twilio Voice or Messages as a webhook, start your dev server and start an ngrok tunnel in the same command with the `ngrok` flag. For example: `twilio serverless:start --ngrok=""`

### Deploy your Function

To deploy your Function and have access to live url(s), run `twilio serverless:deploy` from your CLI. This deploys your Function(s) to Twilio under a development Environment by default, where they can be accessed from:

`https://<service-name>-<random-characters>-dev.twil.io/<function-path>`

For example: `https://incoming-sms-examples-3421-dev.twil.io/sms-reply`

You can now invoke your Function with HTTP requests, configure it as the [webhook](/docs/usage/webhooks/getting-started-twilio-webhooks) for a Twilio phone number, call it from a Twilio Studio [**Run Function** Widget](/docs/studio/widget-library/run-function), and more.

## Log and return version data

Copy and paste the following example code into your newly minted Function. Ensure that your Function is [public](/docs/serverless/functions-assets/visibility), save your changes, and deploy the Service that contains this Function.

```js title="Log and return versions"
exports.handler = (context, event, callback) => {
  // PATH represents the relative path of this function
  // This value does not include the domain name
  const path = context.PATH;
  const nodeVersion = process.version;
  const twilioVersion = require('twilio/package.json').version;

  console.log(`Function path: ${path}`);
  console.log(`Node.js version: ${nodeVersion}`);
  console.log(`Twilio SDK version: ${twilioVersion}`);

  return callback(null, {
    status: 'complete',
    path,
    nodeVersion,
    twilioVersion,
  });
};
```

While running live logs (click **Enable live logs** in the Console), make a `GET` request to your Function using a tool such as [curl](https://curl.se/) or [Postman](https://www.postman.com/). You will then see logs displaying the Function's path, as well as the versions of Node.js and the Twilio SDK. Your HTTP client will also receive the same data as JSON.

For example, a public Function named `/versions` would log the following (with different versions, depending on when you're reading this):

```bash
Function path: /versions
Node.js version: v14.18.1
Twilio SDK version: 3.72.0
```

It would also return the following JSON response:

```json
{
  "status": "complete",
  "path": "/versions",
  "nodeVersion": "v14.18.1",
  "twilioVersion": "3.72.0"
}
```

> \[!NOTE]
>
> This sample uses `context.PATH` to log the relative path of this Function. There are several other helpful, [built-in process variables](/docs/serverless/functions-assets/functions/variables#default-environment-variables) that you may wish to log as well.