-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Move to ecstatic
v4
#522
Move to ecstatic
v4
#522
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢 🚢 🚢
Looks like there may be a replacement I'd run with that version ASAP (once it's available), but continue this branch to get us on to v4 (as v3's days are clearly numbered...). |
I agree. Thankfully, because we have |
do we have any workaround for now?. I have been seeing the following error since today morning hours. 945 verbose stack ecstatic: No matching version found for ecstatic@^2.0.0 |
Install an old version of ecstatic from GitHub? |
@prabhakerb what version of http-server are you trying to use? Your stack trace should be complaining about looking for |
I am using the http-server 0.10.0 version which installs ecstatic@^2.0.0. |
@prabhakerb once ecstatic publishes a v3 version again, you may want to move to the latest published version of http-server, 0.11.1. Interesting that ecstatic's v2 releases were unpublished as well |
ecstatic has published v3 again, the immediate fire should be out. Because of the unpublishing problems, as well as the comment that ecstatic will stop being maintained in the future, I've made a fork of ecstatic which we might consider switching to. I'm still getting CI running and haven't published yet, but right now it's just a straight up fork. |
Closing in favor of #693 |
This is a new internal branch version of #520, moved here to make multiple contributions simpler. There are breaking changes but we don't yet know what exactly they are. At the moment, simply upgrading to ecstatic v4 causes http-server to stop serving content, but no errors are thrown.
To contribute to moving to ecstatic v4, make PRs against this branch (
use_ecstatic_v4
), notmaster
.Related, ecstatic unpublished their v3.x versions (#521), which is causing fresh installs of http-server to fail. Upgrading to v4 would fix these issues, but it would be better for ecstatic to republish a v3.x version with the security fix (jfhbrook/node-ecstatic#255).
fixes #518, fixes #461, fixes #512, fixes #480