Improve (ba)sh usage, mainly in docs (#634)

* packages/create/scripts/update-template-repo.sh: use env

increases portability

* packages/create/package.json: do not call bash excessively

the script's shebang calls the shell already.
Right now a bash is called within a shell only to execute
the shebang, which in turn executes another shell.

* *: use `sh` instead of `bash` for simple commands

These commands are not bash specific and the docs
should reflect that.

Also some bytes are saved.

Author: fkobi

CONTRIBUTING.md

@@ -16,7 +16,7 @@ Please keep your pull requests focused to feature or issue. Focused smaller chan
 ## Preparing
 This is a monorepo, meaning the repo holds multiple packages. It requires the use of [pnpm](https://pnpm.io/). You can [install pnpm](https://pnpm.io/installation) with:
 
-```bash
+```sh
 npm i -g pnpm
 ```
 
@@ -25,27 +25,27 @@ Linux users, you will have to ensure 'sudo' is not required. See [docker post in
 
 `pnpm` commands run in the project's root directory will run on all sub-projects. You can checkout the code and install the dependencies with:
 
-```bash
+```sh
 cd cli
 pnpm install
 ```
 
 ## Build and run
 To build the project and all packages. Run the 'build' script:
 
-```bash
+```sh
 # from root of project
 pnpm build
 ```
 This outputs into /packages/PACKAGE/dist/.
 
 Run the 'cli' package:
-```bash
+```sh
 pnpm sv
 ```
 
 Run build with watch mode:
-```bash
+```sh
 pnpm dev
 ```
 
@@ -54,29 +54,29 @@ pnpm dev
 For each add-on we have integration tests setup. These install the deps, build the app, run the dev server and then run a few small snippets against the add-on to see if the changes introduced by the add-on are working as expected.
 
 Run all tests:
-```bash
+```sh
 # from root of project
 pnpm test
 ```
 
 Run tests with vitest ui:
-```bash
+```sh
 # from root of project
 pnpm test:ui
 ```
 
 Run package specific tests by specifying a project flag to the package and running the test command. Eg:
-```bash
+```sh
 pnpm test --project core # addons / create / migrate / etc.
 ```
 
 To run a individual test. `cd` into the package. Run the local `test` script to that package, with a path arg to the individual piece you want tested. Eg:
-```bash
+```sh
 pnpm test [path-to-test]
 ```
 
 To debug a failing test. A good starting point is to `cd` into the failing tests dir. Proceed to `build` it. Then `preview` it. From here you will have increased information to help in the debug process. Eg:
-```bash
+```sh
 # Each test is a standalone app
 cd .test-output/addons/[addon-test]/[test-id]
 pnpm build
@@ -91,32 +91,32 @@ There are a few guidelines we follow:
 
 - Ensure `pnpm lint` and `pnpm check` pass. You can run `pnpm format` to format the code
 - linting
-```bash
+```sh
 # from root of project
 pnpm lint
 ```
 - formatting
-```bash
+```sh
 # from root of project
 pnpm format
 ```
 - type checking
-```bash
+```sh
 # from root of project
 pnpm check
 ```
 
 ## svelte-migrate
 To run svelte-migrate locally:
-```bash
+```sh
 # from root of project
 node ./packages/migrate/bin.js 
 ```
 
 ## Generating changelogs
 Only publish a change set if it is in 'sv' or 'svelte-migrate' as all other packages are bundled. 
 For changes to be reflected in package changelogs:
-```bash
+```sh
 # from root of project
 pnpm changeset:publish
 ```

documentation/docs/10-introduction/10-overview.md

@@ -8,7 +8,7 @@ The command line interface (CLI), `sv`, is a toolkit for creating and maintainin
 
 The easiest way to run `sv` is with [`npx`](https://docs.npmjs.com/cli/v8/commands/npx) (or the equivalent command if you're using a different package manager — for example, `pnpx` if you're using [pnpm](https://pnpm.io/)):
 
-```bash
+```sh
 npx sv <command> <args>
 ```
 

documentation/docs/20-commands/10-sv-create.md

@@ -6,7 +6,7 @@ title: sv create
 
 ## Usage
 
-```bash
+```sh
 npx sv create [options] [path]
 ```
 

documentation/docs/20-commands/20-sv-add.md

@@ -6,11 +6,11 @@ title: sv add
 
 ## Usage
 
-```bash
+```sh
 npx sv add
 ```
 
-```bash
+```sh
 npx sv add [add-ons]
 ```
 

documentation/docs/20-commands/30-sv-check.md

@@ -14,13 +14,13 @@ Requires Node 16 or later.
 
 You will need to have the `svelte-check` package installed in your project:
 
-```bash
+```sh
 npm i -D svelte-check
 ```
 
 ## Usage
 
-```bash
+```sh
 npx sv check
 ```
 
@@ -59,7 +59,7 @@ Use this if you only want to check the Svelte files found in the current directo
 
 Files/folders to ignore, relative to workspace root. Paths should be comma-separated and quoted. Example:
 
-```bash
+```sh
 npx sv check --ignore "dist,build"
 ```
 
@@ -75,7 +75,7 @@ If provided, warnings will cause `sv check` to exit with an error code.
 
 A quoted, comma-separated list of `code:behaviour` pairs where `code` is a [compiler warning code](../svelte/compiler-warnings) and `behaviour` is either `ignore` or `error`:
 
-```bash
+```sh
 npx sv check --compiler-warnings "css_unused_selector:ignore,a11y_missing_attribute:error"
 ```
 
@@ -90,7 +90,7 @@ A quoted, comma-separated list of sources that should run diagnostics on your co
 
 Example:
 
-```bash
+```sh
 npx sv check --diagnostic-sources "js,svelte"
 ```
 

documentation/docs/20-commands/40-sv-migrate.md

@@ -8,12 +8,12 @@ Some migrations may annotate your codebase with tasks for completion that you ca
 
 ## Usage
 
-```bash
+```sh
 npx sv migrate
 ```
 
 You can also specify a migration directly via the CLI:
-```bash
+```sh
 npx sv migrate [migration]
 ```
 

documentation/docs/30-add-ons/03-devtools-json.md

@@ -30,7 +30,7 @@ export function handle({ event, resolve }) {
 
 ## Usage
 
-```bash
+```sh
 npx sv add devtools-json
 ```
 

documentation/docs/30-add-ons/05-drizzle.md

@@ -6,7 +6,7 @@ title: drizzle
 
 ## Usage
 
-```bash
+```sh
 npx sv add drizzle
 ```
 
@@ -27,7 +27,7 @@ Which database variant to use:
 - `mysql` — another popular open source database
 - `sqlite` — file-based database not requiring a database server
 
-```bash
+```sh
 npx sv add drizzle=database:postgresql
 ```
 
@@ -39,7 +39,7 @@ The SQL client to use, depends on `database`:
 - For `mysql`: `mysql2`, `planetscale`
 - For `sqlite`: `better-sqlite3`, `libsql`, `turso`
 
-```bash
+```sh
 npx sv add drizzle=database:postgresql+client:postgres.js
 ```
 
@@ -49,6 +49,6 @@ Drizzle is compatible with well over a dozen database drivers. We just offer a f
 
 Whether to add Docker Compose configuration. Only available for [`database`](#Options-database) `postgresql` or `mysql`
 
-```bash
+```sh
 npx sv add drizzle=database:postgresql+client:postgres.js+docker:yes
 ```

documentation/docs/30-add-ons/10-eslint.md

@@ -6,7 +6,7 @@ title: eslint
 
 ## Usage
 
-```bash
+```sh
 npx sv add eslint
 ```
 

documentation/docs/30-add-ons/15-lucia.md

@@ -6,7 +6,7 @@ An auth setup following [the Lucia auth guide](https://lucia-auth.com/).
 
 ## Usage
 
-```bash
+```sh
 npx sv add lucia
 ```
 
@@ -21,6 +21,6 @@ npx sv add lucia
 
 Whether to include demo registration and login pages.
 
-```bash
+```sh
 npx sv add lucia=demo:yes
 ```