-
Notifications
You must be signed in to change notification settings - Fork 132
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
Too many dependencies #63
Comments
I agree with you. I was actually going to start a a new branch.
|
awesome! if you have time, it'd be really neat if you could document/blog somewhere how you extract Chrome's CSS and adapt it for chromeHAR. would be interesting stuff. |
@cvan definitely! @cvan question for you, I was actually going to start a separate project. Mainly because I want to make it on Polymer and I wanted to add random features that aren't really in chrome aka: Flagging non gzip content or flagging none CDN content or non cache content,etc... Which to be fair don't really belong in this project. Thoughts? New repo or we can just make a branch here. I want to do new repo and I'm perfectly happy giving you commit access there too. |
as I'm sure you know, there are lots of tools that already do all that:
but, do you know about Chrome's Network Audits in the Dev Tools? because I think that does exactly what you're talking about. now, if you started a separate and then port all of the other parts of the Chrome Dev Tools to JS :) |
@cvan Yea, I know they do it. But I want to do it all off a single HAR file. All those require you be on the actual page. What i want to do is collect tons of hars and then analysis it later. So yea, it's essentially everything you can do in the panel but at a later time based on a HAR. |
👍 to that. I think that's brilliant. I'd gladly help with that; it aligns with my project's needs. |
Thats definitely stuff we're interested in having inside of Chrome's network panel as well. If you use our latest frontend and build on that, then we would be able to upstream your features. |
Please consider simplifying dependencies or providing a distributable package. Forcing plain users (who do not want to test, just run) to install dependencies likes bower, phantomjs, VCBuild.exe (!!!) is a limit in use and applicability. Thanks.
npm http 304 https://registry.npmjs.org/underscore
‼ pre-build test failed, compiling from source...
‼ pre-build test failed, compiling from source...
x { [Error: getaddrinfo ENOTFOUND] code: 'ENOTFOUND', errno: 'ENOTFOUND', syscal
l: 'getaddrinfo' }
√ jpegtran built successfully!
x { [Error: getaddrinfo ENOTFOUND] code: 'ENOTFOUND', errno: 'ENOTFOUND', syscal
l: 'getaddrinfo' }
√ jpegtran built successfully!
‼ pre-build test failed, compiling from source...
x { [Error: getaddrinfo ENOTFOUND] code: 'ENOTFOUND', errno: 'ENOTFOUND', syscal
l: 'getaddrinfo' }
√ optipng built successfully!
‼ pre-build test failed, compiling from source...
x { [Error: getaddrinfo ENOTFOUND] code: 'ENOTFOUND', errno: 'ENOTFOUND', syscal
l: 'getaddrinfo' }
√ gifsicle built successfully!
? getaddrinfo ENOTFOUND
c:\dev\src\chromeHAR\node_modules\karma\node_modules\socket.io\node_modules\sock
et.io-client\node_modules\ws>node "c:\Program Files\nodejs\node_modules\npm\bin
node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visua
l Studio 2005 or 3) add the location of the component to the system path if it
is installed elsewhere. [c:\dev\src\chromeHAR\node_modules\karma\node_modules
socket.io\node_modules\socket.io-client\node_modules\ws\build\binding.sln]
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visua
l Studio 2005 or 3) add the location of the component to the system path if it
is installed elsewhere. [c:\dev\src\chromeHAR\node_modules\karma\node_modules
socket.io\node_modules\socket.io-client\node_modules\ws\build\binding.sln]
The text was updated successfully, but these errors were encountered: