* add doc about git clean for working around ts issues * Update dev_docs/troubleshooting.mdx Co-authored-by: Spencer <email@spalger.com> * Update dev_docs/troubleshooting.mdx Co-authored-by: Spencer <email@spalger.com> * Update troubleshooting.mdx Co-authored-by: Spencer <email@spalger.com> Co-authored-by: Stacey Gammon <gammon@elastic.co> Co-authored-by: Spencer <email@spalger.com>
This commit is contained in:
parent
2e2964f625
commit
f4af51ada5
28
dev_docs/troubleshooting.mdx
Normal file
28
dev_docs/troubleshooting.mdx
Normal file
|
@ -0,0 +1,28 @@
|
|||
---
|
||||
id: kibTroubleshooting
|
||||
slug: /kibana-dev-docs/troubleshooting
|
||||
title: Troubleshooting
|
||||
summary: A collection of tips for working around strange issues.
|
||||
date: 2021-09-08
|
||||
tags: ['kibana', 'onboarding', 'dev', 'troubleshooting']
|
||||
---
|
||||
|
||||
### Typescript issues
|
||||
|
||||
When switching branches, sometimes the TypeScript cache can get mixed up and show some invalid errors. If you run into TypeScript issues (invalid errors, or if it's taking too long to build types), here a few things to try.
|
||||
|
||||
1. Build TypeScript references with the clean command.
|
||||
|
||||
```
|
||||
node scripts/build_ts_refs --clean
|
||||
```
|
||||
|
||||
2. Restore your repository to a totally fresh state by running `git clean`
|
||||
|
||||
```
|
||||
# dry-run the clean to see what will be deleted
|
||||
git clean -fdxn -e /config -e /.vscode
|
||||
|
||||
# review the files which will be deleted, consider adding some more excludes (-e)
|
||||
# re-run without the dry-run (-n) flag to actually delete the files
|
||||
```
|
Loading…
Reference in a new issue