Skip to content
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

Closed
wants to merge 1 commit into from
Closed

Move to ecstatic v4 #522

wants to merge 1 commit into from

Conversation

thornjad
Copy link
Member

@thornjad thornjad commented May 2, 2019

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), not master.

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

Copy link

@m2hd1 m2hd1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢 🚢 🚢

@BigBlueHat
Copy link
Member

Looks like there may be a replacement ecstatic v3 soon: jfhbrook/node-ecstatic#256

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...).

@thornjad
Copy link
Member Author

thornjad commented May 2, 2019

I agree. Thankfully, because we have ^3.0.0 specified in the published version, a 3.3.2 release from jfhbrook/node-ecstatic#256 should work automatically, and should fix the security vulnerability.

@thornjad thornjad added this to the v0.12.0 milestone May 2, 2019
@prabhakerb
Copy link

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
3945 verbose stack at pickManifest (/usr/local/lib/node_modules/npm/node_modules/npm-pick-manifest/index.js:65:11)
3945 verbose stack at fetchPackument.then.packument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:52:18)
3946 verbose cwd /Users/bobpr01/ppm-ux
3947 verbose Darwin 18.2.0
3948 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
3949 verbose node v10.15.3
3950 verbose npm v6.4.1
3951 error code ETARGET
3952 error notarget No matching version found for ecstatic@^2.0.0
3953 error notarget In most cases you or one of your dependencies are requesting
3953 error notarget a package version that doesn't exist.
3953 error notarget
3953 error notarget It was specified as a dependency of 'http-server'

@brodycj
Copy link

brodycj commented May 2, 2019

do we have any workaround for now?

Install an old version of ecstatic from GitHub?

@thornjad
Copy link
Member Author

thornjad commented May 2, 2019

@prabhakerb what version of http-server are you trying to use? Your stack trace should be complaining about looking for ecstatic@^3.0.0, not 2.0.0

@prabhakerb
Copy link

I am using the http-server 0.10.0 version which installs ecstatic@^2.0.0.

@thornjad
Copy link
Member Author

thornjad commented May 2, 2019

@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

@thornjad
Copy link
Member Author

thornjad commented May 3, 2019

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.

@thornjad
Copy link
Member Author

thornjad commented Jul 6, 2021

Closing in favor of #693

@thornjad thornjad closed this Jul 6, 2021
@thornjad thornjad deleted the use_ecstatic_v4 branch August 9, 2021 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
6 participants