[BUG] Windows instructions include outdated method of running node
See original GitHub issueDescribe the bug
At this page:
https://docs.near.org/docs/local-setup/running-testnet-windows
there are instructions to use the scripts in nearcore in order to start up a local node. That is not the case and we want to always use nearup for starting nodes.
Expected behavior When I land on a page describing how to start a local node, I expect the instructions are up to date.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Error when installing necessary packages on Node js
I am using Node.js. I don't have a json file setup yet for the VSC. The script is edited in VSC and then...
Read more >[BUG] npm install will randomly hang forever and cannot be ...
When running npm install it will sometimes hang at a random point. When it does this, it is stuck forever. CTRL+C will do...
Read more >Tutorial: Node.js on Windows for beginners | Microsoft Learn
A guide to help beginners get started with Node.js development on Windows.
Read more >6 reasons your Node.js apps are failing - IBM Developer
Problems occurring in Node.js application deployments can have a range of symptoms, but can generally be categorized into the following:.
Read more >Switching between Node versions during development
Run the included install.cmd to set up necessary system environment variables. Tip: Detailed installation instructions are available on GitHub.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

any objections to me just blowing away this entire section and rewriting?
justification
nearuphas it’s own repo and in other areas of our docs (APIs for example) we link out to the authoritative resource with (plans for) light treatment of the external content in our docs, but not trying to replace them.re:
nearup, there’s no mention of Windows on that page and, although i spun up a Windows instance locally, i’m not sure how much / if any of this content is needed fornearupactually.recommendation
Machine Setupsection into 3 pages:PR #457 fixes this