Clay Allsopp

medium.com/@clayallsopp · Personal blog · on HN since 2015

Clay Allsopp writes about React Native, Relay, GraphQL and mobile development with JavaScript, plus TypeScript migration.

What HN saysHN commenters point to his guide on incrementally migrating JavaScript to TypeScript, though one found it did not cover ts-loader setups.
15HN people shared it
3linked it in comments
12stories submitted
257story points
8 years agolast shared
2015people per year2026

Most-shared posts

  1. 1
    Relay 101: Building a Hacker News Client
    3 people · 12 points · first shared 2015 · 1 comments on HN
  2. 2
    A first GraphQL Server
    2 people · 119 points · first shared 2015 · 23 comments on HN
  3. 3
    2016: The Year React Native Eats Mobile Development
    2 people · 3 points · first shared 2016 · discussion on HN
  4. 4
  5. 5
    GraphiQL: GraphQL’s Killer App?
    1 people · 88 points · first shared 2016 · 16 comments on HN
  6. 6
    Peer-To-Peer Sharing with the Karma Go
    1 people · 23 points · first shared 2015 · 1 comments on HN
  7. 7
    React Native @ Palantir
    1 people · 6 points · first shared 2015 · discussion on HN
  8. 8
  9. 9
    How to write a JavaScript tutorial
    1 people · 1 points · first shared 2015 · discussion on HN
  10. 10

What HN people wrote when they linked it

gryzzly · 2017-04-13
Anyone got a link on how to transition existing large webpack/React/babel project to using Typescript? Googling I only found https://medium.com/@clayallsopp/incrementally-migrating-javascript-to-… but it doesn’t use ts-loader and doesn’t go into details on how to use typings. I tried following ts-loader docs, but things broke at `import flatten from 'lodash/flatten'` and adding typings for `lodash ` didn’t help. Would be interesting what strategies people use to get it working in existing project.
xtrumanx · 2015-10-08
I'm a big fan of React but it took me a year after its introduction for me to get it and like it. What particularly did the trick for me was one of Pete Hunt's talks he gave a year after release acknowledging the confusion and explaining the reasoning for React rather than just the technology itself. I feel like GraphQL can be something great and the pain points they identify with typical APIs are stuff I've felt but GraphQL just feels incomplete to me. I feel they're focusing too much on what GraphQL looks like on the client-side and not enough what it looks like on the server-side. The biggest question I have is what's going to process the GraphQL query on the server to fetch the data from the actual datastore? What does that look like when working with typical datastore such as a SQL-based database? The closest thing I've seen that answered that question was this blog post[0] which doesn't look very appealing if that's what the server-side implementation is going to look like. The blog post's implementation looks like a more complicated version of my own APIs which are usually a series of custom endpoints based on my client's needs. I don't see the big deal right now. Maybe next year... [0] https://medium.com/@clayallsopp/your-first-graphql-server-3c766ab4f0a2
benthehenten · 2015-08-12
AppHub co-founder here, we realize that this is something that would seem to be prohibited by Apple, but updating JavaScript code is explicitly permitted by the iOS Developer Agreement [1]. This same technology is used by Meteor [2], Trigger.io [3], and Adobe Hydration [4], and also used by Facebook and Palantir [5] in their apps. [1] https://developer.apple.com/programs/ios/information/iOS_Program_Infor… [2] http://info.meteor.com/blog/apple-hot-code-push-mobile [3] https://trigger.io/ [4] http://docs.build.phonegap.com/en_US/tools_hydration.md.html [5] https://medium.com/@clayallsopp/a-dynamic-crazy-native-mobile-future-p…

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close