Nathan Arthur

It appears that the reason it's timing out is that the finished build contains more than 20,000 files (and it's only going to get bigger! This is a big site)....

As far as I can tell Netlify doesn't have a supported method of uploading a zip to deploy via the CLI, so that's probably out. I'm running out of ideas....

Thank you for the information! If I'm understanding correctly, you're asking if I could let Netlify pull the changes using its git integration instead of using your Netlify action. Yes,...

I have found that [the Netlify API does support uploading a zip](https://docs.netlify.com/api/get-started/#zip-file-method), so trying that solution.

Would also be nice to have a rule like this: https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/unbound-method.md I'm running into this issue because the default [ESLint version](https://typescript-eslint.io/rules/unbound-method/) of this rule flags cases like this: ``` expect(my_func).toBeCalled()...

Clearing the cache doesn't strike me as a good solution if you're trying to make sure your users aren't hit with this error. This solution worked for me: https://github.com/anthonyjgrove/react-google-login/issues/132#issuecomment-458029717

Would be great to have this in the library. In the meantime, I extended Jest's matchers myself in my test setup file: ```ts interface CustomMatchers { toAppearBefore: (argument: HTMLElement) =>...

> Alternatively, to be consistent with the behavior of "next month", it should pass the week _number_ and year in `knownValues`, like `next month` produces month and year in `knownValues`...

I had this issue. All I had to do to fix it was quit and restart the test watcher. It was caused because I reinstalled node_modules while the watcher was...

Judging by the event that fires when attempting to click the submit button, I believe the problem may be related to this issue on the iscroll project: https://github.com/cubiq/iscroll/issues/928