# Install Dependencies and Configure Contentstack

### About this export

| Field | Value |
| --- | --- |
| **content_type** | lesson |
| **platform** | contentstack-academy |
| **source_url** | https://www.contentstack.com/academy/courses/contentstack-quick-start/install-dependencies-and-configure-contentstack |
| **course_slug** | contentstack-quick-start |
| **lesson_slug** | install-dependencies-and-configure-contentstack |
| **markdown_file_url** | /academy/md/courses/contentstack-quick-start/install-dependencies-and-configure-contentstack.md |
| **generated_at** | 2026-05-04T05:36:50.588Z |

> Part of **[Contentstack Quick Start](https://www.contentstack.com/academy/courses/contentstack-quick-start)** on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys.

<!-- ai_metadata: {"lesson_id":"06","type":"video","duration_seconds":182,"video_url":"https://cdn.jwplayer.com/previews/8mWAHVVZ","thumbnail_url":"https://cdn.jwplayer.com/v2/media/8mWAHVVZ/poster.jpg?width=720","topics":["Install","Dependencies","and","Configure","Contentstack"]} -->

#### Video details

#### At a glance

- **Title:** Install Dependencies And Configure Contentstack
- **Duration:** 3m 2s
- **Media link:** https://cdn.jwplayer.com/previews/8mWAHVVZ
- **Publish date (unix):** 1716925471

#### Streaming renditions

- application/vnd.apple.mpegurl
- audio/mp4 · AAC Audio · 113747 kbps
- video/mp4 · 180p · 180p · 145831 kbps
- video/mp4 · 270p · 270p · 168830 kbps
- video/mp4 · 360p · 360p · 190069 kbps
- video/mp4 · 406p · 406p · 203807 kbps
- video/mp4 · 540p · 540p · 247489 kbps
- video/mp4 · 720p · 720p · 316525 kbps
- video/mp4 · 1080p · 1080p · 489477 kbps

#### Timed text tracks (delivery)

- **thumbnails:** `https://cdn.jwplayer.com/strips/8mWAHVVZ-120.vtt`

#### Transcript

So, moving along, what we need to do now is install the dependencies for our repository. The first thing that we need to do in the terminal is change directories to the root of the cloned repository. To do this, type cd restaurant-menu-react-app/. Then we're ready to install the dependencies using the Node Package Manager, by typing npm install, then press enter. You can see that there's a minor update available, and that really shouldn't matter in our case. The next step is changing the credential file from .env.sample to just .env. Notice in the editor it's looking for our stack API key, as well as our delivery token, environment, and region. Now before, when we created our token, I showed you that you could easily copy that info. So let's return back to that screen to do just that. I'll jump back to my browser, and in Content Stack we can navigate to Settings. From there we can choose Tokens, then select our restaurant menu token, and if you scroll down you can click the Copy to Clipboard button to copy your stack API key. Then move back to VS Code and paste that value where it currently reads your stack API key. Now you'll need to repeat that process for the delivery token as well, but with the magic of editing, mine is already updated. Next we need to update the name of our environment, which, if you remember, we called Development. So I'll type that in. Finally, my region is AWS North America, so based on the comments here, I need to set my region to US. Now let's see this app render on our local host. To do this, I'll create a new terminal window to avoid clutter. I have to make sure I'm in the correct directory, so for my purposes, I need to type CD and then I'll reference our restaurant menu React app. To run this on our local server, all you have to do is type npm start. It might take a few seconds, but as it starts the development server, your browser will open. Here, I have to allow VS Code to open Chrome, so I'll do that, and when I do, sure enough, after a few seconds, the app will load. Now that we have it running locally, the next step is to deploy our app using Launch.

#### Subtitles (WebVTT)

```webvtt
WEBVTT

1
00:00:00.000 --> 00:00:08.180
So, moving along, what we need to do now is install the dependencies for our repository.

2
00:00:08.180 --> 00:00:13.200
The first thing that we need to do in the terminal is change directories to the root

3
00:00:13.200 --> 00:00:15.660
of the cloned repository.

4
00:00:15.660 --> 00:00:24.800
To do this, type cd restaurant-menu-react-app/.

5
00:00:24.800 --> 00:00:29.960
Then we're ready to install the dependencies using the Node Package Manager, by typing

6
00:00:29.960 --> 00:00:37.440
npm install, then press enter.

7
00:00:37.440 --> 00:00:41.380
You can see that there's a minor update available, and that really shouldn't matter

8
00:00:41.380 --> 00:00:42.880
in our case.

9
00:00:42.880 --> 00:00:51.640
The next step is changing the credential file from .env.sample to just .env.

10
00:00:51.640 --> 00:00:57.480
Notice in the editor it's looking for our stack API key, as well as our delivery token,

11
00:00:57.480 --> 00:00:59.920
environment, and region.

12
00:00:59.920 --> 00:01:06.320
Now before, when we created our token, I showed you that you could easily copy that info.

13
00:01:06.320 --> 00:01:10.520
So let's return back to that screen to do just that.

14
00:01:10.520 --> 00:01:16.560
I'll jump back to my browser, and in Content Stack we can navigate to Settings.

15
00:01:16.560 --> 00:01:23.280
From there we can choose Tokens, then select our restaurant menu token, and if you scroll

16
00:01:23.280 --> 00:01:30.720
down you can click the Copy to Clipboard button to copy your stack API key.

17
00:01:30.720 --> 00:01:39.200
Then move back to VS Code and paste that value where it currently reads your stack API key.

18
00:01:39.200 --> 00:01:44.880
Now you'll need to repeat that process for the delivery token as well, but with the magic

19
00:01:44.920 --> 00:01:49.000
of editing, mine is already updated.

20
00:01:49.000 --> 00:01:55.520
Next we need to update the name of our environment, which, if you remember, we called Development.

21
00:01:55.520 --> 00:01:57.320
So I'll type that in.

22
00:01:57.320 --> 00:02:03.480
Finally, my region is AWS North America, so based on the comments here, I need to set

23
00:02:03.480 --> 00:02:07.900
my region to US.

24
00:02:07.900 --> 00:02:12.320
Now let's see this app render on our local host.

25
00:02:12.320 --> 00:02:17.360
To do this, I'll create a new terminal window to avoid clutter.

26
00:02:17.360 --> 00:02:24.920
I have to make sure I'm in the correct directory, so for my purposes, I need to type CD and

27
00:02:24.920 --> 00:02:30.920
then I'll reference our restaurant menu React app.

28
00:02:30.920 --> 00:02:37.320
To run this on our local server, all you have to do is type npm start.

29
00:02:38.320 --> 00:02:43.040
It might take a few seconds, but as it starts the development server, your browser will

30
00:02:43.040 --> 00:02:44.040
open.

31
00:02:44.040 --> 00:02:51.880
Here, I have to allow VS Code to open Chrome, so I'll do that, and when I do, sure enough,

32
00:02:51.880 --> 00:02:55.640
after a few seconds, the app will load.

33
00:02:55.640 --> 00:03:00.960
Now that we have it running locally, the next step is to deploy our app using Launch.

```

```transcript
<!-- PLACEHOLDER: replace with real transcript before publish if cues were auto-derived from WebVTT -->
[00:00] So, moving along, what we need to do now is install the dependencies for our repository.
[00:08] The first thing that we need to do in the terminal is change directories to the root
[00:13] of the cloned repository.
[00:15] To do this, type cd restaurant-menu-react-app/.
[00:24] Then we're ready to install the dependencies using the Node Package Manager, by typing
[00:29] npm install, then press enter.
[00:37] You can see that there's a minor update available, and that really shouldn't matter
[00:41] in our case.
[00:42] The next step is changing the credential file from .env.sample to just .env.
[00:51] Notice in the editor it's looking for our stack API key, as well as our delivery token,
[00:57] environment, and region.
[00:59] Now before, when we created our token, I showed you that you could easily copy that info.
[01:06] So let's return back to that screen to do just that.
[01:10] I'll jump back to my browser, and in Content Stack we can navigate to Settings.
[01:16] From there we can choose Tokens, then select our restaurant menu token, and if you scroll
[01:23] down you can click the Copy to Clipboard button to copy your stack API key.
[01:30] Then move back to VS Code and paste that value where it currently reads your stack API key.
[01:39] Now you'll need to repeat that process for the delivery token as well, but with the magic
[01:44] of editing, mine is already updated.
[01:49] Next we need to update the name of our environment, which, if you remember, we called Development.
[01:55] So I'll type that in.
[01:57] Finally, my region is AWS North America, so based on the comments here, I need to set
[02:03] my region to US.
[02:07] Now let's see this app render on our local host.
[02:12] To do this, I'll create a new terminal window to avoid clutter.
[02:17] I have to make sure I'm in the correct directory, so for my purposes, I need to type CD and
[02:24] then I'll reference our restaurant menu React app.
[02:30] To run this on our local server, all you have to do is type npm start.
[02:38] It might take a few seconds, but as it starts the development server, your browser will
[02:43] open.
[02:44] Here, I have to allow VS Code to open Chrome, so I'll do that, and when I do, sure enough,
[02:51] after a few seconds, the app will load.
[02:55] Now that we have it running locally, the next step is to deploy our app using Launch.
```

#### Key takeaways

- Connect **Install Dependencies and Configure Contentstack** back to your stack configuration before moving to the next module.
- Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment.
- Re-read the delivery versus management boundary for anything you changed in the entry model.

## Supplement for indexing

### Content summary

Install Dependencies and Configure Contentstack. Install Dependencies and Configure Contentstack in Contentstack Quick Start (contentstack-quick-start).

### Retrieval tags

- Install
- Dependencies
- and
- Configure
- Contentstack
- contentstack-quick-start
- lesson 06
- Install Dependencies and Configure Contentstack
- contentstack-quick-start lesson

### Indexing notes

Index this lesson as a primary chunk tagged with lesson_id "06" and topics: [Install, Dependencies, and, Configure, Contentstack].
Parent course slug: contentstack-quick-start. Use asset_references URLs as thumbnail hints in search results when present.
Never surface LMS quiz content or assessment answers from this file.

### Asset references

| Label | URL |
| --- | --- |
| Video thumbnail: Install Dependencies and Configure Contentstack | `https://cdn.jwplayer.com/v2/media/8mWAHVVZ/poster.jpg?width=720` |

### External links

| Label | URL |
| --- | --- |
| Contentstack Academy home | `https://www.contentstack.com/academy/` |
| Training instance setup | `https://www.contentstack.com/academy/training-instance` |
| Academy playground (GitHub) | `https://github.com/contentstack/contentstack-academy-playground` |
| Contentstack documentation | `https://www.contentstack.com/docs/` |
