We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I update giscus-react from 2.2.2 to 2.2.3, my react project building crashed:
I'm not sure if my case is the same with #782.
I'm using Giscus in such way:
const Giscus = require('@giscus/react')
Then I print 'Giscus' in project with console.log:
giscus-react in 2.2.2 it prints a function as follow:
giscus-react in 2.2.3 it prints a path as follow:
【advice】If the build product changes commit, is it better to upgrade with BREAK CHANGE?
The text was updated successfully, but these errors were encountered:
MuYunyun/create-react-doc@f181ae0
fix: giscus/giscus-component#783
b3b54d7
Fixed in #810, released in v2.2.4.
Sorry, something went wrong.
4c3b386
No branches or pull requests
What happened?
When I update giscus-react from 2.2.2 to 2.2.3, my react project building crashed:
I'm not sure if my case is the same with #782.
Debug
I'm using Giscus in such way:
Then I print 'Giscus' in project with console.log:
giscus-react in 2.2.2 it prints a function as follow:
giscus-react in 2.2.3 it prints a path as follow:
Environment
Others
【advice】If the build product changes commit, is it better to upgrade with BREAK CHANGE?
The text was updated successfully, but these errors were encountered: