question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Windows instructions include outdated method of running node

See original GitHub issue

Describe 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:closed
  • Created 3 years ago
  • Comments:6 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
amgandocommented, May 29, 2020

any objections to me just blowing away this entire section and rewriting?


image


justification

  • there’s lots of redundant info here that’s covered elsewhere
  • much of this content are from legacy pages that i kept from the old state of docs for fear of blowing something away i didn’t understand
  • nearup has 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 for nearup actually.

recommendation

  1. turn this into an epic that includes the following
  • refactor Machine Setup section into 3 pages:
    • Choose a network (new content)
    • Choose a development stack (like this and this merged sensibly together)
    • Development lifecycle (like this)
  • test on 3 major operating systems
  • test on multiple version of node?
  • test with feedback from community members?
  1. pair on completing the epic with 1 person running macOS, 1 person running Windows (and 1 person testing alignment on Linux afterwards)
0reactions
thisisjoshfordcommented, Nov 13, 2020

PR #457 fixes this

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found