Images optimizations crash #18946
Comments
|
Can you try It should fail gracefully with an error linking to https://github.com/vercel/next.js/blob/canary/errors/install-sharp.md |
|
@styfle Looks like we have some errors on new canary : |
|
Can you share your babel configuration ( |
|
No issue with the previous stable version, even without babel/preset-react, it's just when I bump to canary as requested by stylfe. But in case here are my config {
"name": "brand-website",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "NODE_OPTIONS='--inspect' next dev",
"build": "next build",
"start": "next start",
"export": "next export",
"typescript:lint": "eslint . --ext .js,.jsx,.ts,.tsx",
"typescript:lint-fix": "eslint . --ext .js,.jsx,.ts,.tsx --fix",
"typescript:typescheck": "tsc -p tsconfig.json --noEmit"
},
"dependencies": {
"@next/bundle-analyzer": "^10.0.1",
"@tailwindcss/typography": "^0.2.0",
"@tailwindcss/ui": "^0.7.2",
"classnames": "^2.2.6",
"date-fns": "^2.8.1",
"firebase": "^8.0.1",
"i18next": "^19.0.1",
"i18next-browser-languagedetector": "^6.0.1",
"next": "^10.0.2-canary.10",
"next-compose-plugins": "^2.2.0",
"next-optimized-images": "^3.0.0-canary.10",
"next-seo": "^4.7.3",
"prismic-javascript": "^3.0.2",
"prismic-reactjs": "^1.3.3",
"react": "^17.0.1",
"react-cookie-consent": "^6.1.0",
"react-dom": "^17.0.1",
"react-i18next": "^11.2.3",
"react-syntax-highlighter": "^15.2.1",
"react-transition-group": "^4.4.1",
"swr": "^0.3.1",
"tailwindcss": "^1.9.5"
},
"devDependencies": {
"@types/classnames": "^2.2.10",
"@types/node": "^14.6.0",
"@types/react": "^16.9.13",
"@types/react-syntax-highlighter": "^13.5.0",
"@typescript-eslint/eslint-plugin": "^4.6.1",
"@typescript-eslint/parser": "^4.6.1",
"eslint": "^7.7.0",
"eslint-config-prettier": "^6.11.0",
"eslint-plugin-jsx-a11y": "^6.3.1",
"eslint-plugin-prettier": "^3.1.4",
"eslint-plugin-react": "^7.20.6",
"eslint-plugin-react-hooks": "^4.1.0",
"husky": "^4.2.4",
"lint-staged": "^10.1.3",
"postcss-preset-env": "^6.7.0",
"prettier": "^2.0.5",
"typescript": "^4.0.2"
},
"author": {
"name": "Andréas HANSS"
}
} |
|
I ran into this and it is due to next-optimized-images and optimized-images-loader using an older version of I don't have a solution to fix it. I tried installing the master branch of optimized-images-loader but couldn't get it to build. |
timneutkens
added
kind: story
and removed
bug
|
Just had the same problem where |
Worked for me. Thank you! |
God thank you @tomafro... I was struggling with the same under It was working on production build, but I was so tired of having to make one build each time I wanted to test something using images because of a conflict between What I did (if it can help anyone):
Et voilà everithing is now working like a charm |
|
Can you try |
|
Closing since this was fixed a year ago |
|
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Bug report
Describe the bug
When I migrate to next 10, I'm using the new component image with the following config (image is from prismic CMS)
Image URL is
https://images.prismic.io/blaze/c5975c62-4bd8-4151-8e04-d6837add38c4_sequencing-article-image.png?auto=compress,formatfrom prismic.System information
The text was updated successfully, but these errors were encountered: