chore: release v1.0.0 (#30)

* chore: release v1.0.0

* Update CHANGELOG.md

* chore: typo

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Aleksandr Grenishin <nd0ut.me@gmail.com>

Author: github-actions[bot]

CHANGELOG.md

@@ -1,3 +1,18 @@
+# [1.0.0](https://github.com/uploadcare/nextjs-loader/compare/v0.4.0...v1.0.0) (2022-11-22)
+
+
+### Features
+
+* add a `getBlurDataURL` server-side helper to generate base64 blurred placeholder ([5404d56](https://github.com/uploadcare/nextjs-loader/commit/5404d564e211aee6a633dfb272de71e0c4c0ce85))
+* add separate `loader.js` module entry to be used with Next.js v13 `loaderFile` setting ([a6577b7](https://github.com/uploadcare/nextjs-loader/commit/a6577b7cca4c5a7b8ddf26beb29ad9ddc9a261f6))
+
+
+### BREAKING CHANGES
+
+* previously implemented `blurDataURL` auto-generation won't work in Next.js v13. It was a bad way because the blurry image was requested from the server in runtime. A new way is to generate a blurry image base64 string at build time using `getBlurDataURL`. See [README](https://github.com/uploadcare/nextjs-loader#when-src-is-a-string).
+
+
+
 # [0.4.0](https://github.com/uploadcare/nextjs-loader/compare/v0.3.3...v0.4.0) (2022-06-08)
 
 

README.md

@@ -209,7 +209,7 @@ There are two possible use cases:
 
 If you pass `placeholder="blur"` to the `Image` or `UploadcareImage` component, the `blurDataURL` property will be used as the placeholder. In this case you must provide the `blurDataURL` property using our `getBlurDataURL` server-side helper.
 
-Here is the ``getBlurDataURL` interface:
+Here is the `getBlurDataURL` interface:
 
 ```ts
 function getBlurDataURL(

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uploadcare/nextjs-loader",
-  "version": "0.4.0",
+  "version": "1.0.0",
   "description": "Uploadcare custom image loader for Next.js",
   "main": "./build/index.js",
   "types": "./build/index.d.ts",