Twitter | Search | |
MJ @ React Rally
Working on . Co-author React Router. Built . Head over heels for
28,834
Tweets
1,187
Following
42,933
Followers
Tweets
MJ @ React Rally 5h
Replying to @Swizec
The original module is a bunch of methods that fetch from the npm registry. But the mock just grabs files from the filesystem.
Reply Retweet Like
MJ @ React Rally 5h
Replying to @Swizec
I was able to achieve this in Jest by mocking out the module making the fetch calls. Check out
Reply Retweet Like
MJ @ React Rally 12h
😂😂😂
Reply Retweet Like
MJ @ React Rally 15h
Also, thank you for taking the time to try and understand and speak to my real concern 🙏
Reply Retweet Like
MJ @ React Rally 15h
Thank you. I think you're right. When I see the type errors I'm so bugged about it that I feel like I have to go and fix everything immediately. Probably just need to practice ignoring them for a while while I figure things out.
Reply Retweet Like
MJ @ React Rally 15h
You are a noble champion of TypeScript, my friend. Don't change.
Reply Retweet Like
MJ @ React Rally 15h
You mean forgetting the punchline to jokes?
Reply Retweet Like
MJ @ React Rally 16h
Replying to @disjfa
Mmm, maybe. Thanks, I had forgotten about that one. I'll check it out!
Reply Retweet Like
MJ @ React Rally 16h
Replying to @mjackson
I've been using nodemon, but it seems like it's scenario-solved for the use case of starting a server from a file. Not a great node API.
Reply Retweet Like
MJ @ React Rally 16h
Replying to @gmonteith
Since anti-patterns do not exist I would have to disagree. Oatmeal cookies are, in fact, real. 🙃
Reply Retweet Like
MJ @ React Rally 16h
Searching for a good npm package I can use for restarting a server that isn't based on a file-system watcher. I've got some code in memory and I wanna use it to start a server, but then when it changes I wanna restart the server.
Reply Retweet Like
MJ @ React Rally 16h
Ya, I think that's the approach I'd have to take. But I have such an obsessive personality I'm afraid I'd get all caught up in doing stuff that just doesn't matter.
Reply Retweet Like
MJ @ React Rally 18h
Replying to @BenLesh @ryanflorence
The main blocker for me right now is that I think faster than I can type things, and sometimes my ideas aren't even fully formed when I'm writing code, so taking the time to type something that will probably change both interrupts my thought process and feels like a waste.
Reply Retweet Like
MJ @ React Rally Aug 20
Replying to @tarang9211
Yep, completely agree. I've been busy the past few weeks with JS Conf and React Rally this week, so I haven't had much time for coding. Planning on being able to dive in again next week.
Reply Retweet Like
MJ @ React Rally Aug 20
Replying to @benmvp @ryanflorence
Reply Retweet Like
MJ @ React Rally Aug 20
Replying to @KevinDavus
😢 Very sorry to hear this, Kevin. ❤️ to you and the rest of the family.
Reply Retweet Like
MJ @ React Rally Aug 20
Replying to @benmvp @ryanflorence
I don't think it'll be that hard, actually. I already write propTypes for everything I ship. So generating Flow and TS types should be a very simple, automated step. No room for error or things getting out of sync.
Reply Retweet Like
MJ @ React Rally Aug 20
That's kind of what I'm thinking too 👍
Reply Retweet Like
MJ @ React Rally Aug 20
Replying to @ryanflorence
At this point I'm convinced I need to ship types for everything I publish. No doubt. Still not convinced I need to actually *use* TS though. Sucks some of the joy out of programming for me.
Reply Retweet Like
MJ @ React Rally Aug 20
Replying to @AndrewJLeedham
Ya I think that's what it was 🤦‍♂️
Reply Retweet Like