Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cpojer
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
91.
▲
by
cpojer
10y ago
As Sebastian said we are more than excited to explore what we can improve in the future. If you are interested, please start a discussion on the GitHub issue tracker: https://github.com/yarnpkg/yarn :)
92.
▲
by
cpojer
10y ago
Can you make yarn out of hair?
93.
▲
Yarn – A new package manager for JavaScript
(code.facebook.com)
1714 points
by
cpojer
10y ago
|
469 comments
94.
▲
JavaScript Testing with Jest 16.0: Turbocharged CLI and Community Update
(facebook.github.io)
11 points
by
cpojer
10y ago
|
0 comments
95.
▲
by
cpojer
10y ago
You can use Jest together with enzyme! We posted a big community update together with Jest 16 which should highlight a bunch of ways that you can test with Jest. https://facebook.github.io/jest/blog/2016/10&#x
96.
▲
by
cpojer
10y ago
Hey! I'm Christoph and I work on Jest. We wrote a blog post about how we are making Jest fast: facebook.github.io/jest/blog/2016/03/11/javascript-unit-testing-performance.html If your test is fully CPU bou
97.
▲
by
cpojer
10y ago
The only thing that Jest has in common with Jest from a year ago is the name. We rewrote the entire framework incrementally (as all the blog posts on the Jest blog point out). We still do not support browser testing. We don't believe t
98.
▲
Jest 15: New Defaults for Jest
(facebook.github.io)
24 points
by
cpojer
10y ago
|
5 comments
99.
▲
Jest 14.0: React Tree Snapshot Testing and React Native Support
(facebook.github.io)
4 points
by
cpojer
10y ago
|
0 comments
100.
▲
JavaScript Unit Testing Performance
(facebook.github.io)
6 points
by
cpojer
11y ago
|
0 comments
101.
▲
Evolving Complex Systems Incrementally
(youtube.com)
1 points
by
cpojer
11y ago
|
0 comments
102.
▲
Relay and Routing
(medium.com)
11 points
by
cpojer
11y ago
|
0 comments
103.
▲
by
cpojer
11y ago
We are not using php-v8js for server rendering at FB.
104.
▲
by
cpojer
11y ago
We are experimenting with it and I've built a service for JS at FB. I'm convinced that server rendering should be transparent to a product developer – ie no special work should be required and the server rendering infra should dec
105.
▲
Relay Technical Preview
(facebook.github.io)
474 points
by
cpojer
11y ago
|
106 comments
106.
▲
Effective JavaScript Codemods
(medium.com)
8 points
by
cpojer
11y ago
|
1 comments
107.
▲
by
cpojer
12y ago
no.
108.
▲
by
cpojer
12y ago
Start talking about your implementation! It'll be a shame if you have worked on this for so long but no one else ever gets to see it. The world is a big place, chances are there is always someone else doing the exact same thing you are
109.
▲
by
cpojer
12y ago
https://www.youtube.com/watch?v=9sc8Pyc51uU - there are some examples in the talk from React JS Conf. We haven't yet finalized what API we will provide when we open source Relay. You'll certainly get one object, c
110.
▲
by
cpojer
12y ago
Relay will be same as React. Including React-Native of course – almost nothing in Relay is browser specific (except for routing). (source: I'm an engineer on Relay)
111.
▲
Breaking the Web with JavaScript
(medium.com)
11 points
by
cpojer
12y ago
|
0 comments