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.
Upgrade perttier new version v1.13.2
See original GitHub issueThe latest version of prettier is v1.13.2.
But when I fork this repo and run npm install prettier@1.13.2 on my local machine.
The npm will update a lot of version in package-lock.json.
My npm version is 6.0.1.
My node version is 10.1.0
Do you have any suggestion about upgrade the prettier version? Thanks.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:6 (3 by maintainers)
Top Results From Across the Web
prettier - npm
Prettier is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that...
Read more >react-base-table | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >[1.2 - 1.4] Modular Rocket Systems v1.13.2 (2018-03-12)
Modular Rocket Systems Parts Pack Cooperates with other mods: TweakScale FAR / NEAR AVC (Add-on Version Checker) RemoteTech2 Engine Ignitor ...
Read more >Documentation | U.S. Web Design System (USWDS)
We recommend using npm to make it as straightforward as possible to install the design system and update it as we release new...
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
Seems it also will be 1.13.4 soon 😃
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.