David Good

Another use case: using Chrome inspect to debug TypeScript code. I don't think there's a straightforward way to do it today. Never got `babel-node` with `inspect` working, but I think you can set debuggers in and run the transpiled code and source maps are still for TS files

Thought of this while working with library/API code samples which weren't typed and had to dig for the significance of function parameters. I assume the omission of types was to reduce build/bundle complexity and focus on demoing the lib/API. But what if that wasn't an axcuse?

And if TypeScript is supported in the #backend and #frontend, it wouldn't be much of a leap for it to become part of #ECMAscript

With @pikapkg showing us what a buildless/bundleless future looks like, this would align nicely with that vision.

By browser support I mean parsing and ignoring types. I don't think there would be much of a performance hit, but if so, it could be behind a flag and used exclusively for #development.

With @deno_land bringing @typescript support to the server side, is it only a matter of time until browsers support #TypeScript? @MSEdgeDev @GoogleChromeDev @FirefoxDevTools #JavaScript #NodeJS

Not sure why the docs don't mention `state` at all. It seems like a pretty important part of securing OAuth

Maybe validating `state` is something the developer is meant to do manually since the `state` would have to be saved for each user's session?

It seems like @passportjs doesn't validate `state` on #OAuth callback. If I enable state, go thru auth worflow for Google, then grab the callback URL, modify the state param, and request that URL, it still succeeds. Can anyone confirm? #security #JavaScript

How often do you think the emergency call button gets pressed accidentally?

chrome://settings/ > Privacy and security > Site Settings > Cookies and site data > Cookies and site data > See all cookies and site data chrome://settings/siteData @googlechrome #Chrome

So the #GCP Credentials #OAuth consent screen is scarier than it sounds. Most of the fields can be left blank. You can get external access even for sensitive scopes. You'll just get a scary warning before the OAuth callback. You can then create an ID with a localhost cb for dev

Oh wow, just discovered @GCPcloud Cloud Shell and deployed an app with a few commands and without leaving the browser. What a treat! What else have I been missing out on? #cloud #paas #treat

React Native The Hard Way 1. Learn #iOS development 2. Learn #Android development 3. Learn #ReactNative This is why I never build anything meaningful

Bringing an idea to life using @GCPcloud was outrageously easy. Especially appreciated the attention to detail in the #NodeJS libraries: error messages contain links to troubleshooting steps or even directly to the project's console where a feature needs to be enabled