Quickstart

Bob is an AI SDLC (Software Development Lifecycle) partner that augments your existing workflows. In this tutorial, you will learn some of Bob's core features by modernizing a TypeScript Express API from Node.js 16 to Node.js 22. You do not need experience in Node.js or TypeScript to complete the tutorial. You will learn how Bob analyzes dependencies and modernizes code patterns.

Bob provides four essential capabilities that you will use while upgrading the API:

• Modes: Specialized personas that tailor Bob's behavior for specific tasks.
• Context mentions: Reference specific project elements in conversations with Bob, such as files, folders, or Git commits.
• Approval workflow: Review every tool Bob plans to use before it executes.
• Literate coding: Write code with Bob directly in your editor. Type instructions in plain language right where the code should go.

This tutorial uses a TypeScript Express REST API as the example project. However, you do not need experience in Node.js or TypeScript.

To complete this tutorial, you need the following:

Launch IBM Bob and clone the example repository to begin working with the Node.js application you will modernize.

In the Bob chat panel at the bottom right of the window, enter the following prompt to navigate to the express-todo-api folder. Bob will ask you to allow it to run the change directory command. Click the Run action to let Bob change directories:

Bob changes to the express-todo-api folder. Bob's responses may vary slightly from the examples in this tutorial, but the key information is the same. Bob responds by confirming that it navigated to the directory, and describing the contents.

Create a Dockerfile to run the application in a containerized environment, eliminating the need to install Node.js or dependencies locally.

Before modernizing, verify that the legacy code builds and runs correctly. This baseline ensures you can identify any issues the modernization introduces.

During the build phase, Bob will tell you that the build failed because the Dockerfile uses npm ci, which requires a package-lock.json file that doesn't exist.

In the Bob chat panel, tell Bob to build and test the application.

Bob asks you to save a change to the Dockerfile that will fix the package-lock.json issue with the following message:

Bob's ability to detect and fix build errors is an example of how it works with you to troubleshoot and resolve issues during deployments.

Once Bob applies the fix and finishes the build, it gives you the following output:

You and Bob verified the legacy application is working correctly.

Before modernizing, click the mode selector dropdown and switch to Bob's Ask mode. Ask mode can only read files, so you can safely explore code without accidentally making changes. You can also type /ask in Bob chat to change to Ask mode.

Bob supports @ context mentions that let you reference specific files, folders, or problems directly in your prompts. Context mentions give Bob precise information about what you want to discuss.

Explore the package.json, tsconfig.json, and Dockerfile files by explicitly telling Bob which files to analyze using @ mentions. Learning about these files helps you understand the modernization requirements before you make any changes.

In the Bob chat panel, run the following prompt:

The @ symbol tells Bob to include package.json as context. Bob doesn't start answering immediately; it explores your codebase first, reading files, following patterns, and analyzing code. Don't interrupt this exploration phase.

Bob identifies the following updates needed for Node.js 22:

Ask Bob to analyze the project's TypeScript configuration:

Bob responds with the following components that you need to update for Node.js 22:

Ask Bob to analyze the project's Dockerfile:

Bob responds with what needs to be updated for Node.js 22:

You now understand what needs updating. In the next section, you switch to Code mode and have Bob make the changes.

Bob determined the following modernization requirements for package.json, tsconfig.json, and Dockerfile:

• Change Node.js 16 to Node.js 22 in package.json and Dockerfile
• Update the TypeScript compiler target and module settings
• Fix outdated dependency versions

To start modernizing the application, switch back to Code mode so Bob can make code changes. Click the mode selector and select Code, or type /code in the chat.

In the Bob chat panel, run the following modernization prompt. Notice the @ references that point Bob to the specific files it works on:

Bob gives you a summary of all components it updated in the modernization:

You and Bob have modernized the application.

Use Bob's literate coding feature to update the sample todo title, marking the app as modernized. Literate coding lets you write instructions in plain language directly in your editor instead of using the chat panel.

You've updated the API using literate coding. When you test the API in the following section, you see this new title in the API response.

Verify the code modernization and your literate code change by rebuilding and testing the Docker container.

Switch back to Code mode and describe what you want Bob to verify:

Once Bob verifies the application has been modernized, it gives you the following summary:

The API works correctly, and the title is updated to "Welcome to the Modernized Node.js 22 API", confirming that Bob preserved existing behavior while modernizing the Node.js version and dependencies.

In this tutorial, you learned how to modernize an Express API from Node.js 16 to Node.js 22 using Bob. Bob analyzed your dependencies, updated configuration files, and modernized the Docker setup while preserving all functionality.

• Learn about Bob's Code review feature /review to catch potential issues before you commit your work.
• Learn about modes, which are specialized personas that tailor Bob's behavior for your specific tasks.
• Learn how to use Bob's chat interface which is the main way to interact with Bob.