Visit /images/test.svg for original.
\nVisit /images/test.svg?width=50&format=jpeg to see optimization (50px wide JPEG).
\nVisit /images/test.svg?height=20&fit=cover for another optimization.
\nVisit /images/test.svg?quality=50&format=webp for WebP with lower quality.
\n `);\n});\n\nconst PORT = process.env.PORT ?? 8000;\napp.listen(PORT, () => {\n console.log(`Hastily demo server listening on http://localhost:${PORT}`);\n console.log(`Serving images from: ${imageDir}`);\n});","lang":"typescript","description":"This quickstart sets up an Express server with `hastily` to serve and optimize images from a local `www/images` directory, demonstrating basic usage of the `imageopto` middleware with Fastly-compatible URL parameters. It includes setup for a dummy image file for immediate testing."},"warnings":[{"fix":"Run `npm install sharp` in your project's root directory. For specific environments (e.g., M1 Macs, Alpine Linux), consult `sharp`'s documentation for installation caveats.","message":"Hastily requires `sharp` as a peer dependency. You must install `sharp` separately in your project (`npm install sharp`). Failure to do so will result in runtime errors. Ensure `sharp` is compatible with your Node.js version and architecture, as it relies on native binaries.","severity":"gotcha","affected_versions":">=0.1.0"},{"fix":"Ensure the image files have supported extensions (e.g., `.jpg`, `.png`, `.webp`, `.svg`). Verify that your static file server is setting correct `Content-Type` headers for image responses. You might need to provide a custom `filter` function to `imageopto()` if your setup is non-standard.","message":"By default, `hastily.imageopto()` only processes requests that it determines to be uncompressed images (based on URL extension and `Content-Type` header). If your images are not being transformed, verify the request URL and response headers.","severity":"gotcha","affected_versions":">=0.1.0"},{"fix":"Consult the `hastily` GitHub repository and npm changelog for specific breaking changes in new minor versions and adjust your code accordingly. Consider pinning to exact minor versions until 1.0 release.","message":"As `hastily` is currently in pre-1.0 development (v0.5.0), minor version updates may introduce breaking API changes without a major version increment. Always review release notes when updating.","severity":"breaking","affected_versions":">=0.1.0"},{"fix":"Implement robust HTTP caching headers (`Cache-Control`, `ETag`, `Last-Modified`) for optimized images. Consider using a reverse proxy or CDN to cache common image variations. Monitor server resource usage and scale accordingly.","message":"Image processing with `sharp` (and thus `hastily`) is CPU and memory intensive. Running `hastily` in a production environment without proper caching strategies (e.g., HTTP caching, CDN caching) or adequate server resources can lead to significant performance degradation or out-of-memory errors, especially under heavy load.","severity":"gotcha","affected_versions":">=0.1.0"}],"env_vars":null,"last_verified":"2026-04-23T00:00:00.000Z","next_check":"2026-07-22T00:00:00.000Z","problems":[{"fix":"Run `npm install sharp` in your project's root directory. Ensure that `sharp` installs successfully without compilation errors specific to your system.","cause":"`sharp` is a peer dependency of `hastily` and must be installed manually by the consumer.","error":"Error: Cannot find module 'sharp' from '![/images/test.svg](\"/images/test.svg\"){kind=link}
![/images/test.svg?width=50&format=jpeg](\"/images/test.svg?width=50&format=jpeg\"){kind=link}
![/images/test.svg?height=20&fit=cover](\"/images/test.svg?height=20&fit=cover\"){kind=link}
![/images/test.svg?quality=50&format=webp](\"/images/test.svg?quality=50&format=webp\"){kind=link}