[Warning?] Are readme instructions somehow harmfull?
See original GitHub issueI executed:
npm install --save react-native-device-info
It made my whole repository environment stop working. I had to execute npm install
again, and here’s the output:
added 794 packages, removed 2 packages and updated 33 packages in 63.55s
I’m yet adapting myself to react-native and even npm itself. But it seems to me that readme instructions made me downgrade my modules and even removed hundreds of stuff from here!
So if I’m mistaken or did something wrong, please tell me – it is my best interest to understand more about it. Otherwise, isn’t better to put a warning there or something? Maybe tell people to run npm install
right after this installation step? Idk.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
[Markdown] An option to highlight a "Note" and "Warning ...
The idea of GitHub-flavored Markdown changing the semantics of a <blockquote> is hilarious and also bad. This would mean your Markdown isn't supported...
Read more >How to make a styled Markdown admonition box in a GitHub ...
Which Renders like this: ⚠ WARNING: Aliens are coming. A description of the colour, smell and dangerous behaviour of the aliens.
Read more >Handbook Markdown Guide - GitLab
Additional Information; Warnings; Danger; Do's and Don'ts ... Read through the Blog Formatting Guidelines for further information.
Read more >AsciiDoc Writer's Guide | Asciidoctor
Here's a simple rule to help you differentiate the two: ... Use WARNING to inform the reader of danger, harm, or consequences that...
Read more >PySimpleGUI
This User's Manual (also the project's readme) is one vital part of the PySimpleGUI programming environment. The best place to read it is...
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 FreeTop 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
Top GitHub Comments
I had the same issue. Removed node_modules and re-ran npm install.
Now I have the another problem after running the link command.
Update: So … linking broke everything. Even xCode would not open the project. Thankfully I had a backup. Evidently, from what I’ve read, the original creator does not really have time to maintain this. What a shame. I was super excited about it. I am going to look for something else. I do not have high hopes though
Sorry, I never replied. I didn’t have any problems using this either time.