Jul 29, 2020
Translating engineering into captivating digital experiences. Know more at:Â https://www.cygnet-infotech.com/frontend-engineering-services
Loading...
seen from United States
seen from United States
seen from United States
seen from United States
seen from Mexico
seen from Latvia
seen from United Kingdom
seen from United States
seen from United Kingdom
seen from Canada
seen from United States
seen from Iraq
seen from Germany
seen from United States
seen from Netherlands
seen from United States
seen from United Kingdom
seen from United States
seen from Kazakhstan
seen from China
Translating engineering into captivating digital experiences. Know more at:Â https://www.cygnet-infotech.com/frontend-engineering-services
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Develop to Design - A guide to emergency design for front-end developers
Develop to Design – A guide to emergency design for front-end developers
I will be talking about develop to design a guide to emergency design for front-end developers. This talk is primarily aimed at developers working in small teams who find hiring a designer too expensive, or for people who are interested in designing the experience for their own products. The experience of using an application starts even before registration, and it has to be maintained even when…
View On WordPress
npm memory usage
We noticed our build process was using over a gig of ram and traced it back to npm. Our npm build is fairly straightforward, and our project size is on the small side. 700 MB for just npm install, and another 500 MB or so for WebPack. WebPack’s memory usage, I can understand. But 700 MB just to download some packages? Seems excessive.
The solution we’ve come up with for now is to launch `npm install` from our build script, and then run webpack as a separate build task instead of launching webpack as an npm postinstall step. Lame, but effective. Takes our peak memory consumption from ~1200 MB to ~700 MB.
An interesting, unconventional approach to building maintainable CSS. I think it makes a ton of sense.
I don’t use CSS preprocessors they way many people do. Here’s an attempt to explain why.
I agree with this sentiment for a slightly different reason... CSS is relatively straightforward, whereas SCSS can be incredibly obscure. However, I do like using SCSS simply as a mechanism of file organization...Â
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
A good intro to Webpack
A good intro to webpack. Written from a Rails perspective, but really handy for anyone who’s just starting out. I’ve found the webpack docs to be a bit dense, and this really helped.
Tlite, tooltips in < 650 bytes of JavaScript.
At work, we were using a jQuery tooltip library, but it didn’t play nice with dynamically added elements (e.g. the React portions of our app). Besides, I’d like to totally get rid of jQuery at some point, since we are using React.
That’s how Tlite was born. Tooltips without the dependency on jQuery, customizable, and really lightweight footprint.
...And using developer tools, you can emulate IE9. Makes cross-browser testing not suck so much.