Can yarn be considered a viable option as a substitute for gazebo and npm?

I must clarify that I am not so good at beginner tools, so I apologize in advance if I ask for something obvious and stupid.

So far I have used bower for the end of the font and npm for the server side, although each of the mentioned tools has its own advantages, and I mean the flat bower dependency management (reduces the load from the client) and npm nested dependency management (helps a lot with version control ), it has become quite cumbersome to use so many tools (web package, browser, etc.). Perhaps I used these tools incorrectly and could use any of them with some option (unknown to me) and only scratched the surface, I just took this answer as my rule of thumb, and have been doing it since I read it. It would be great if I could reduce at least these two to one.

Recently, I have become curious that the yarn and all the hype around it seems that it is doing fine and as if completely replacing npm. When I read the documents, I found the -flat option, and this made me wonder if it can be used as a replacement stand too? If so, can I have either a flat or nested dependency manager (just having multiple json files for the server and front end)?

I would really appreciate it if someone could point me in the right direction!

+6
source share
2 answers

It depends on your specific use case, but ... maybe .

, -, , Webpack Browserify (, , npm ) Bower. NPM Bower Browserify vs. Gulp Grunt vs. Webpack, , Webpack Bower.

, , HTTP, JavaScript, ( Bower). Webpack Browserify ( ) - .

: HTTP/2 , . . Webpack HTTP/2 , HTTP/2.

npm , , - Webpack/Browserify, , .

npm v3, , . : , , , .

+7

- , npm.

, 100% , , , 1000 , . npms . , .

. , , . 10- .

. npm shrinkwrap, - , .

+2

Source: https://habr.com/ru/post/1016701/


All Articles