cpojer

10 ms·

1. 61.▲
   My Perfect Development Environment(cpojer.net)

   1 points by cpojer 4y ago|0 comments
2. 62.▲
   Building a JavaScript Testing Framework(cpojer.net)

   2 points by cpojer 4y ago|0 comments
3. 63.▲
   Set up a new Mac, Fast(cpojer.net)

   3 points by cpojer 4y ago|0 comments
4. 64.▲
   by cpojer 4y ago

   Jest supports multiple “projects” in a single invocation, and they can all use a different reporter. You can define a base config for your repo, and then inherit two sub-configs from it each with different runners and mutually exclusive sel
5. 65.▲
   by cpojer 4y ago

   Hi! Christoph from Jest here. Your feedback is great, and 100% valid. Jest was built a long time ago when ES modules did not exist, and we are still carrying some of that legacy baggage around. The good news is that we have never been shy a
6. 66.▲
   Dependency Managers Don’t Manage Your Dependencies(cpojer.net)

   17 points by cpojer 5y ago|2 comments
7. 67.▲
   by cpojer 5y ago

   Those are all great bundlers/dev servers but they aren’t as ambitious as Rome. Rome aims to be the one tool that handles everything: compiling, bundling, testing, linting and everything else.
8. 68.▲
   by cpojer 5y ago

   The JavaScript tooling ecosystem is fragmented, bloated and slow. Rome is the best - and currently only - bet to fix this. I’m excited!
9. 69.▲
   Inclusion in a Distributed World(cpojer.net)

   2 points by cpojer 5y ago|0 comments
10. 70.▲
    A Management Starter Pack(cpojer.net)

    3 points by cpojer 6y ago|0 comments
11. 71.▲
    Principles of Developer Experience(cpojer.net)

    2 points by cpojer 6y ago|0 comments
12. 72.▲
    Hermes: A JavaScript engine optimized for mobile apps starting with React Native(code.fb.com)

    7 points by cpojer 7y ago|0 comments
13. 73.▲
    Hermes: A Lightweight JavaScript Engine Optimized for React Native on Android(hermesengine.dev)

    10 points by cpojer 7y ago|3 comments
14. 74.▲
    Microsoft Officially Launches React Native for Windows(reddit.com)

    4 points by cpojer 7y ago|0 comments
15. 75.▲
    React Native at F8 and Open Source Podcast(facebook.github.io)

    18 points by cpojer 7y ago|1 comments
16. 76.▲
    React Native, 3 years later(artsy.github.io)

    1 points by cpojer 8y ago|0 comments
17. 77.▲
    React Native Open Source Update(facebook.github.io)

    234 points by cpojer 8y ago|114 comments
18. 78.▲
    Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions(code.facebook.com)

    262 points by cpojer 9y ago|44 comments
19. 79.▲
    How to build a JavaScript package manager(yarnpkg.com)

    121 points by cpojer 9y ago|17 comments
20. 80.▲
    Intro to React Native for an iOS Developer(artsy.github.io)

    7 points by cpojer 9y ago|1 comments
21. 81.▲
    by cpojer 9y ago

    Yarn has a "--mutex" option for exactly this purpose.
22. 82.▲
    by cpojer 10y ago

    Indeed. I also spoke about this topic a lot: https://www.youtube.com/watch?v=d0pOgY8__JM
23. 83.▲
    JavaScript Testing with Jest: Jest 18, in-browser repl, future plans(facebook.github.io)

    4 points by cpojer 10y ago|0 comments
24. 84.▲
    by cpojer 10y ago

    Thanks! That's great. Maybe you can help us upgrade then? Jest is fun to contribute to.
25. 85.▲
    by cpojer 10y ago

    Hi! I work on JavaScript Tools at FB. There is a fantastic post by Ben McCormick about the up and downsides of this system: http://benmccormick.org/2016/09/19/testing-with-jest-snapsho... Snapshots aren'
26. 86.▲
    by cpojer 10y ago

    I work on Jest at FB. * I agree regexes suck but that's all we had five years ago when it was started. Would love to move to a glob system incrementally but most of that will have to come from the community. I'm also still concern
27. 87.▲
    by cpojer 10y ago

    How's your lockfile, yo!
28. 88.▲
    by cpojer 10y ago

    Hey, I work on Yarn and Jest. Let me respond to why we built Jest: It solves a ton of problems no other test runner solves and it works well at Facebook's scale. We open sourced it more than two years ago but only recently started to p
29. 89.▲
    by cpojer 10y ago

    We don't think this way. We needed to solve this problem for Facebook, explored alternatives and made the case to build Yarn. We work at Facebook to solve Facebook's engineering challenges; when we can collaborate with other compa
30. 90.▲
    by cpojer 10y ago

    You are right, we aren't 100% compatible right now. Please track the issues on the Yarn GitHub repo that you linked or better yet: help us fix it. This is a community project and we are excited for the community to jump in and help us