ᴙɘɘᴙgYmɘᴙɘj

very helpful, thanks

#180 shows how to go back, but it doesn't return the new route object.

[This](https://github.com/fridays/next-routes/blob/master/src/index.js#L110-L113) shows how some of the [core methods](https://github.com/zeit/next.js/blob/canary/packages/next-server/lib/router/index.js#L20) have been wrapped. There is no core method for `pop`. The underlying next/router is exposed, though, so you can simply call [`Router.back`](https://github.com/zeit/next.js/blob/canary/packages/next-server/lib/router/router.js#L131-L133)...

I see you've updated package.json. (c5596fc7ba69ecd0ed21e64a83aa8a85847cb91c) Is this on npm now?

done 284fb6579e791963a511036e3c115e7ada948168

https://github.com/jasonsalzman/react-add-to-calendar/blob/master/src/helpers/index.js#L50-L55 This is not currently true. `et` can be used for end time (and [_should_ be for events over 100 hours](https://github.com/InteractionDesignFoundation/add-event-to-calendar-docs/blob/master/services/yahoo.md#et)). There are other issues with end times not respecting...

**Extra Info** In `fallbackError` we're throwing errors created with [hapi/boom](https://hapi.dev/module/boom/api/?v=9.1.2). If we throw ApolloErrors, we can specify the `extensions.code`. It still seems like the basic "Not Authorised!" response should use...

I'm seeing the same with "allowJs" and "checkJs". nm - needed to add `include` option as well. ```json { "compilerOptions": { "allowJs": true, "checkJs": true }, "include": [ "**/*.js" ]...

I can move on with my life now. :D

just saw #89 and #88 🙄