Recommended changes

pull/1615/head
Robert Hall 6 years ago
parent b1fd1d4f2a
commit 8aabc7210d

1
.gitignore vendored

@ -12,7 +12,6 @@ node_modules
/test/sourcemaps/samples/*/output.js
/test/sourcemaps/samples/*/output.js.map
/src/compile/shared.ts
/package-lock.json
/store.umd.js
/yarn-error.log
_actual*.*

@ -156,23 +156,22 @@ npm run dev
### Linking to a Live Project
You can then continue to make changes locally to the Svelte project and test it against a local project. For a quick project that takes almost no setup, use the default [sapper-template](https://github.com/sveltejs/sapper-template) project, which employs both Svelte and [Sapper](https://sapper.svelte.technology/). Instructions on setting up the default Sapper template are found in the [repo page](https://github.com/sveltejs/sapper-template).
You can make changes locally to Svelte and test it against any Svelte project. You can also use a [default template](https://github.com/sveltejs/template) for development. Instruction on setup are found in that project repository.
From the root of your local svelte git checkout:
```bash
cd svelte
npm link
```
Then, to link from `sapper-template` or any other given project:
Then, to link from your Svelte project:
```bash
cd sapper-template
```
cd your-svelte-project
npm link svelte
```
You should be good to test changes locally.
And you should be good to test changes locally.
### Running Tests

5056
package-lock.json generated

File diff suppressed because it is too large Load Diff
Loading…
Cancel
Save