You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So if I understand you correctly, the problem that this solves is: "npm install results in a huge node_modules folder, which is 馃憥"
I'm not sure if that's true, or at least it doesn't have to be. Frontend dependencies usually only end up making up a small part of your node_modules tree. And if you have any dev deps, they you're already npm installing anyway.
You are correct on both counts, understanding the original issue and the way you are thinking about node_modules being small for front end dependencies.
I guess I am wanting to solve huge npm deps problem without realizing most of them are actually devDevependencies.
Anyways, thanks for taking time to provide your feedback.
First off, I want to give you guys props for this awesome project. Great Work 馃帀 馃帀
The more I use
@pika-web
, I feel like I should be able to skip NPM install step altogether.Why would you want to do that?
This is why:
![1_liNzl2MQKqg4tLMCF4jY5g](https://user-images.githubusercontent.com/802242/55676322-f1ad3380-5887-11e9-9cda-b3e50ea37860.png)
I am meaning to write full RFC on this, but wanted to throw quick thought to get some feedback.
Oh BTW, I did some exploration on this in #33
The text was updated successfully, but these errors were encountered: