Damian Mooyman

I made an effort to add these in a fork of the module for testing. Here's the major commit where I add these values https://github.com/pixelfusion/pannellum-react/commit/37418415e578a67611cf872e6a4ab048836e9855

Latest version ^5 works fine with next.js. Suggest to close this issue. :) I did not need dynamic imports. I did have to manually add this to my _app.js though...

Thanks @achingbrain I'm using this in my github action and it seems to work well (will report if I run into any rate limiting issues). ``` npm install -g \...

Looks like I spoke too soon. I have the issue even with the suggested fork. However, even with retry and delay rate limit errors are still possible. ``` [1:55:15 AM]...

@achingbrain is there an issue with the way I'm deploying your fix, or is the fix legitimately not catching the rate limiting?

Thanks for getting back to me. For now i'm using `semantic-release || true` in my release scripts, because even if github fails, my code still gets deployed in that case...

For context this is the kind of `output.stderr` that can be encountered during linting. ``` [error] src/components/Icon/Icon.stories.tsx: SyntaxError: ',' expected. (32:3) [error] 30 | }, [error] 31 | }, [error]...

Pushed a check to stderr. Below is an example of the check running against my own (failing) codebase. Previously this error would cause a 422 pushing the check to github,...

Unit tests presented :)

Probably will be addressed / made obsolete with 5.0, hopefully with react CMS pages section. :)