-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove unused deps from extension. #140
Conversation
➡️🐘⬅️ |
The following devDependencies from
basically not having duplicates in |
And since all of them are devDeps, maybe avoid declaring them in The only problem could be the following and do we require support for this ? npm install lighthouse-extension
npm run build |
Hey @boopathi, thanks for the insight! Let me provide you with some of the motivations for the current structure. So the idea is that someone can work on the extension in isolation from the main code. Think of it as a sub project within the main project. By requiring an isolated set of dependencies and no shared knowledge of each other from the parent or the child this sub project keeps its isolation. So depending on the parent for npm deps would violate this principle and actually make the install process slower for everyone since if we bubbled up all the deps to the parent everyone would have to install them to work on the project, vs the current situation where a user has to only install these deps when they are working on the extension. |
@@ -9,9 +9,7 @@ | |||
"build": "gulp build" | |||
}, | |||
"devDependencies": { | |||
"babel-core": "^6.5.2", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the babel
task doesnt change at all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nope! since we are using gulp-babel we are all set
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
afd2612
to
55626ce
Compare
@samccone But, for |
Fixes #110
The real slowness here can be primarily blamed on npm3 not on any single dep.. soo until other things are finally resolved this is just the reality that we will have to deal with.