AWS에서 "sharp" module 설치 에러

이걸로 2일동안 S3 지웠다가 설치하고 람다 다시 세팅하고 했었는데.... 진작에 이글을 봤었으면 금방해결되었을것을... 저는 한참을 삽질했네요..ㅠ.ㅠ 만약 해매시는 분들을 위해 링크도 남깁니다 (체크할) https://github.com/lovell/sharp/issues/2169 https://sharp.pixelplumbing.com/install 그리고 GIF 파일은 sharp에서 변환 지원이 안되네요..^^;;

front 서버에서 next 빌드할때 웹팩 에러가 발생합니다..ㅠ.ㅠ

아... 제가 습관적으로 npm audit 를 해서 버전업이 되서 그런것 같습니다 ..^^;;;; 선생님 코드에서 몇가지 수정한것만 붙여넣으니 빌드가 잘 됩니다 답변 감사합니다!

front 서버에서 next 빌드할때 웹팩 에러가 발생합니다..ㅠ.ㅠ

답변감사합니다 제로초 선생님. 확인해보니 4.41로 되어있어서, 링크처럼 package.json에서 4.28로 설치하고 package-lock.json 을 확인해보니 4.29로 웹팩이 설치되었는데 여전히 같은 에러가 발생합니다..ㅠ.ㅠ //////////////////////////////////////// root@ip-172-31-16-162:/home/ubuntu/testAWS/front# cat package-lock.json | grep "webpack" "webpack-bundle-analyzer": "3.0.3" "autodll-webpack-plugin": { "resolved": "https://registry.npmjs.org/autodll-webpack-plugin/-/autodll-webpack-plugin-0.4.2.tgz", "webpack-merge": "^4.1.0", "webpack-sources": "^1.0.1" "compression-webpack-plugin": { "resolved": "https://registry.npmjs.org/compression-webpack-plugin/-/compression-webpack-plugin-2.0.0.tgz", "webpack-sources": "^1.0.1" "autodll-webpack-plugin": "0.4.2", "webpack": "4.29.0", "webpack-dev-middleware": "3.6.0", "webpack-hot-middleware": "2.24.3", "webpack-sources": "1.3.0", "webpack": { "resolved": "https://registry.npmjs.org/webpack/-/webpack-4.29.0.tgz", "terser-webpack-plugin": "^1.1.0", "webpack-sources": "^1.3.0" "webpack-sources": { "resolved": "https://registry.npmjs.org/webpack-sources/-/webpack-sources-1.3.0.tgz", "terser-webpack-plugin": { "resolved": "https://registry.npmjs.org/terser-webpack-plugin/-/terser-webpack-plugin-1.4.3.tgz", "webpack-sources": "^1.4.0", "webpack": { "resolved": "https://registry.npmjs.org/webpack/-/webpack-4.42.1.tgz", "terser-webpack-plugin": "^1.4.3", "webpack-sources": "^1.4.1" "webpack-ant-icon-loader": { "resolved": "https://registry.npmjs.org/webpack-ant-icon-loader/-/webpack-ant-icon-loader-1.0.8.tgz", "webpack-bundle-analyzer": { "resolved": "https://registry.npmjs.org/webpack-bundle-analyzer/-/webpack-bundle-analyzer-3.0.3.tgz", "webpack-cli": { "resolved": "https://registry.npmjs.org/webpack-cli/-/webpack-cli-3.3.11.tgz", "webpack-dev-middleware": { "resolved": "https://registry.npmjs.org/webpack-dev-middleware/-/webpack-dev-middleware-3.6.0.tgz", "webpack-log": "^2.0.0" "webpack-hot-middleware": { "resolved": "https://registry.npmjs.org/webpack-hot-middleware/-/webpack-hot-middleware-2.24.3.tgz", "webpack-log": { "resolved": "https://registry.npmjs.org/webpack-log/-/webpack-log-2.0.0.tgz", "webpack-merge": { "resolved": "https://registry.npmjs.org/webpack-merge/-/webpack-merge-4.2.2.tgz", "webpack-sources": { "resolved": "https://registry.npmjs.org/webpack-sources/-/webpack-sources-1.4.3.tgz", ///////////////////////////////////

왜 user/0가 본인이 검색되는 거죠 ?

저도궁금했었는데 해결됬네요 감사합니다

질문이요.

제가 제대로 이해한건진 모르겠지만... views/main.pug 에서 요청한건 프런트라고보고 routes/index.js 에서 요청한건 서버라고 볼때 main.pug에선 frontSecret 키를 보내고 index.js 에서는 clientSecret 키를 보내면 api 쪽의 v2.js 에서 if문으로 나눠서 프런트와 서버키를 구분해서 처리하면 될것 같아요