-
Notifications
You must be signed in to change notification settings - Fork 684
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
Bad upgrade path from TJ’s serve #59
Comments
To make it clear: You're talking about that |
@derhuerst Exactly |
That docs still say it is called |
npm info serve@1.4.0 author
# TJ Holowaychuk <tj@vision-media.ca> npm info serve@2.0.0 author
# leo |
This should probably be mentioned in the docs of tj/serve. |
In fact I currently solved it by installing 1.x. |
According to the SemVer spec, we acted just right. Consider this change a complete rewrite of the package (which, in turn, is considered a major/breaking SemVer change). Please use the old version of the package, if you'd like to take advantage of the functionalities that existed before the "rewrite". 😊 |
@yuchi Would you submit a PR at tj/serve to clarify in the docs that |
@leo that's right. Obviously right. But a small note should do the job. |
@derhuerst I will. |
Hallo!
Nice to see
serve
is having a new function! But I see stuff breaking because I expected it to just be a new version of the package, which is not.Could you at least give some information if someone is trying to render Jade files and similar that this is not that
serve
?The text was updated successfully, but these errors were encountered: