rooty/Bootstrap
0
0
Fork 0
mirror of https://github.com/twbs/bootstrap.git synced 2024-12-01 13:24:25 +01:00
Code Issues Actions Packages Releases Activity

Docs: Fix typo Getting Started > Vite and Webpack guides (#37153)

Browse Source 
* 'were to look' → 'where to look'

Co-authored-by: Julien Déramond <juderamond@gmail.com>
This commit is contained in:
Gabriel R. Barbosa 2022-09-14 16:28:10 -03:00 committed by GitHub
parent 3bd5756414
commit 9af1232c65
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
site/content/docs/5.2/getting-started/vite.md
View File

@ -73,7 +73,7 @@ At this point, everything is in the right place, but Vite won't work because we
With dependencies installed and our project folder ready for us to start coding, we can now configure Vite and run our project locally.
1. **Open `vite.config.js` in your editor.** Since it's blank, we'll need to add some boilerplate config to it so we can start our server. This part of the config tells Vite were to look for our project's JavaScript and how the development server should behave (pulling from the `src` folder with hot reload).
1. **Open `vite.config.js` in your editor.** Since it's blank, we'll need to add some boilerplate config to it so we can start our server. This part of the config tells Vite where to look for our project's JavaScript and how the development server should behave (pulling from the `src` folder with hot reload).
<!-- eslint-skip -->
```js

2
site/content/docs/5.2/getting-started/webpack.md
View File

@ -75,7 +75,7 @@ At this point, everything is in the right place, but Webpack won't work because
With dependencies installed and our project folder ready for us to start coding, we can now configure Webpack and run our project locally.
1. **Open `webpack.config.js` in your editor.** Since it's blank, we'll need to add some boilerplate config to it so we can start our server. This part of the config tells Webpack were to look for our project's JavaScript, where to output the compiled code to (`dist`), and how the development server should behave (pulling from the `dist` folder with hot reload).
1. **Open `webpack.config.js` in your editor.** Since it's blank, we'll need to add some boilerplate config to it so we can start our server. This part of the config tells Webpack where to look for our project's JavaScript, where to output the compiled code to (`dist`), and how the development server should behave (pulling from the `dist` folder with hot reload).
```js
const path = require('path')