Jesse Hoffman

@electronicbits I have done something like this in the past and it can work. This precludes you from using the Amplify client SDK though, so all those helpful features and...

I think this would still leave out the case where you had a typo in an aliased import right? Since the typo would still pass the rule, built ultimate fail?

Also filed an issue over at the alias plugin because I am not sure where the change would be needed: https://github.com/johvin/eslint-import-resolver-alias/issues/20

Currently having this same issue in a Lerna monorepo, did #35 go stale?

I was just thinking about how I might need to expand to show different language implementations. It's good to know there is a way to do it, docs def need...

Just chiming in also on this feature. I love this lib for design system documentation, and if feels like a lack of search is holding it back from being a...

@IcanDivideBy0 this was a better solution then checking server. It ensures our markup remains consistent on both **client and server** renders. Not sure if there is anything `react-lazyload` could do...

I'm able to provide a workaround for this by setting the `routed` to true for the base page: ```js # gatsby-node.js exports.onCreatePage = ({ page, actions }) => { const...

I wonder if possibly the `isRedirect` logic in the `page-wrapper` could also check for if the path matches the page contexts `matchPath`, and if so, don't redirect?

Nothing proposed yet @tmskrtsz, other than the workarounds above. I suspect there is a fix related to how `isRedirect` is assigned in the code, but I have not taken a...