André Cruz

For now, I will revert to generate a single CSS file like we were doing before.

Once we find the correct strategy to do what's described in the issue, we may manually revert some parts of these commits: - https://github.com/moxystudio/react-with-moxy/commit/1d6f418879d83ab4b21b617cf63bb5f918bc826a - https://github.com/moxystudio/react-with-moxy/pull/114/commits/28646ea5ab6a296c3b51cd89c631793b3714422c

It's hard for people to know all the good practices, e.g.: force progressive jpgs. On the other hand, this will slow down the building and dev experience :( See: https://github.com/itgalaxy/imagemin-webpack

After investigating, the issue is with `JSON.stringify` here: https://github.com/linkedin/sepia/blob/master/src/util.js#L339 Node 4 and Node 6 have discrepancies in the way they output unicodes.. one simply output as text and other as...

After analyzing sepia, it seems there's no such feature. Would you guys be interested in adding it?

I've made a workaround: ``` js // tests/util/sepia.js 'use strict'; const http = require('http'); const https = require('https'); const originalRequests = { http: http.request, https: https.request }; const sepia =...

I've managed to solve this with `onPopupAlign`: ``` js // ./util/placeArrow.js import positions from 'positions'; const placementsMap = { tc: 'top center', bc: 'bottom center', cl: 'center right', cr: 'center...

Hello @vicchirino, check this out: https://github.com/npms-io/npms-www/tree/master/src/shared/components/tooltip. The tooltip component is using utils/placeArrow and utils/checkEdges

@frrist Discussify doesn't guarantee persistency yet in case there are no peers to serve you the comments data. This is explained in the "disclaimer" part in the description of Chrome...

You may find the description in the Chrome Web Store page: https://chrome.google.com/webstore/detail/discussify/bfmnjjkobeboejeocbompgljbiafbgcc We will be publishing it to Firefox soon too. Maybe it's worth adding a little bit about what...