Skip to content

Releases: vercel/serve

7.1.5

30 May 22:12
@leo leo
Compare
Choose a tag to compare

Patches

  • Added charset to Content-Type header: #394

7.1.4

30 May 18:52
@leo leo
Compare
Choose a tag to compare

Patches

  • Ensured that everything in README.md is correct: #392

7.1.3

30 May 18:35
@leo leo
Compare
Choose a tag to compare

Patches

  • Bumped middleware to the latest version: #391

7.1.2

30 May 09:55
@leo leo
Compare
Choose a tag to compare

Patches

  • Bumped our dependencies to the latest version: #388

7.1.1

29 May 11:23
@leo leo
Compare
Choose a tag to compare

Patches

  • Added example of using the middleware: #385

7.1.0

29 May 10:44
@leo leo
Compare
Choose a tag to compare

Minor Changes

  • Re-added --single and made --listen support ports: #384

Patches

  • Fixed "URL is not defined" error: #381
  • Bumped serve-handler to the latest version: #383

Credits

Huge thanks to @jaeseok-park for helping!

7.0.1

28 May 20:04
@leo leo
Compare
Choose a tag to compare

Patches

  • Removed useless dependencies: #377

7.0.0

28 May 17:10
@leo leo
Compare
Choose a tag to compare

This release marks a completely fresh start for this project.

Over the years, the core of the package has gotten bigger and bigger, eventually containing features that should not be part of it at all. This led to serve becoming rather slow in certain situations. But not just in terms of serving requests, but also when installing (because of the dependency count).

As of today, the package is going into a completely new direction and we're re-evaluating any feature suggestions we're encoutering on the repository.

If you want to continue using the old serve, please lock it like this in your dependencies:

{
  "serve": "6.5.8"
}

Notice that the version number is not prefixed with ^.

However, for those of you who would like to upgrade, there are plenty amazing things awaiting you:

  • The core is now very lean, therefore fast to install and serving requests faster.
  • The package is now powered by serve-handler, which means you can finally customize the entire behavior of all the routes of your static project.
  • Later today, static deployments running on Now will work with the same configuration as serve – right out of the box: Use serve for development and Now in production.

If you have any suggestions, let us know in the issue list or create a pull request to fix something! 🙏

Thank you all for using serve and have a great day!

Leo – @notquiteleo

6.5.8

22 May 14:25
@leo leo
Compare
Choose a tag to compare

Patches

  • Bumped dependencies to the latest version: #371

6.5.7

14 May 19:33
@leo leo
Compare
Choose a tag to compare

Patches

  • Updated update-check package to the latest version: #362
  • Fixed chrome warning and removed unused variable: #364
  • Ensure serve starts even when update check fails: #360
  • Adjusted engines field to match readme: #366

Credits

Huge thanks to @MiniGod, @sreeramjayan and @n0v1 for helping!