this most likely won't clear up the start error, just double checking
<!--
When creating a new PR, please do the following:
* Reference the issue number if there is one, e.g.:
Fixes #Issue_Number
The "Fixes #nnn" syntax in the PR description allows GitHub to automatically close the issue when this PR is merged.
NOTE: This is a comment; please type your descriptions above or below it.
-->
* overview
* whats new to end
* fix migration node
* split fundamentals, move to end
* glob & loc, get started
* security node name
* security section
* azure, client-side, host
* several more sections
* redistribute tutorials
* proofread fixes
* move how to download section
* index files delete and redirect
* fix errors
* reorder some nodes
* scott feedback, flatten main tutorials node
* fix missed feedback items + other issues
* unflatten tutorials node
* move 'how to download'
* more tutorials node tweaks
* standardize view sample links
* db --> DB
* fix build error
* remove link from a parent node
* streamline node names
* xref links
* typos
* typo
* typos and revert some xref links
* scott feedback
* scott feedback
* feedback
* change node name
* safe storage-->protect
Fixes#9219
@JunTaoLuo Dan calls out the implicit versioning "for 2.1 SDK or later;" however, we don't usually version the doc content by SDK release. We might need to say something for this update in the passage that I'm adding to the All topic (*aspnetcore/fundamentals/metapackage.md*) about which SDK version this applies to. I don't know if that's something that you would like to do or what version to call out.
I also remove the version from the samples. We also assume that devs are using the latest SDK with our samples.
Addresses #8579
I might be getting the hang of **_find and replace_** now. 😝
This doesn't touch a couple that ref 2.2.0. I'll tidy those up on https://github.com/aspnet/Docs/issues/8518 after 2.2 RTM.
* Update BrowserLink instructions for 2.0 to 2.1
Upgrading an ASP.NET Core project from 2.0 to 2.1 requires one to manually add the BrowserLink package.
* Update using-browserlink.md
* npm test directory wrong
Running the command in the project root complains that no package.json can be found. You have to run the command from the ClientApp directory where the package.json is located also indicated in the instructions on the splash page "The ClientApp subdirectory is a standard Angular CLI application. If you open a command prompt in that directory, you can run any ng command (e.g., ng test), or use npm to install extra packages into it."
* Minor edits
* Note about task runner explorer option
The gulp file has to be in the root directory or in the directory with package.json not in any subdirectory.
* verbiage tweaks
KKostov
Scott Addie
Curt Cullens
Luke Latham
Rick Anderson
Tom Dykstra
haidelber
David Pine
Maira Wenzel
Scott Addie
Harald Nagel
user135711
Jaxel Rojas