-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
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
Publishing 0.21.10 on npm #1380
Comments
Hi, sorry for slow response, as soon as we resolve #1379 we'll republish! |
Where?? |
any update , .. 7 months later? |
Are there still any plans to update? |
Any news? We are in 2025 now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's been a little over 3 months since 0.21.10 has been released here on GitHub but it doesn't seem to be published on npm. Is there any ETA on when this will happen or is there some kind of blocker? I'm mainly asking because it seems to fix the bug I've filed at #1323 and I'm really looking forward to having it fixed :)
Directly using the GitHub release didn't really work for me, as the npm release seems to bundle vendor code in the dist folder, which needs to be manually imported. I was also wondering why this is necessary, as it doesn't seem very Webpack-like to do it that way.
The text was updated successfully, but these errors were encountered: