Skip to content

Commit

Permalink
Merge pull request #935 from ayushn21/upgrade-guide-patch
Browse files Browse the repository at this point in the history
Add note to update the package manager in the rakefile
  • Loading branch information
ayushn21 authored Nov 8, 2024
2 parents fd90692 + 55dae9b commit 646c42f
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions bridgetown-website/src/_docs/installation/upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,8 @@ We also recommend you run `bin/bridgetown esbuild update` so you get the latest

Bridgetown uses NPM now by default, rather than Yarn, for frontend package managing. You may continue to use Yarn on your existing projects, but if you'd like to switch to NPM, you can simply delete your `yarn.lock` file, run `npm install` (shorthand: `npm i`), and check in `package-lock.json` instead. You can also use [pnpm](https://pnpm.io) if you prefer. Bridgetown is now compatible with all three package managers.

You'll also need to update the `:frontend` tasks in your project's `Rakefile` to use your preferred package manager.

### Specifying Liquid (if necessary) 💧

The default template engine for new Bridgetown sites is ERB, with Liquid being optional. If you're upgrading a site that expects Liquid to be the default template engine, you will need to add `template_engine :liquid` to your `config/initializers.rb` file (or `template_engine: liquid` to `bridgetown.config.yml`). If you don't even have a `config/initializers.rb` file in your project yet, see the below section under **Upgrading to Bridgetown 1.2**.
Expand Down

0 comments on commit 646c42f

Please sign in to comment.