Deploy failing under 3.5.0
See original GitHub issueI just upgraded to component: "@sls-next/serverless-component@3.5.0"
and and am deploying with npx @sls-next/serverless-patched --debug
. I am also on Next.js 12.0.1
I am now receiving error:
[Error: ENOENT: no such file or directory, stat '/home/runner/.serverless/components/registry/npm/@sls-next/serverless-component@3.5.0/node_modules/@sls-next/core/dist/sharp_node_modules'] {
Previously was working on @sls-next/serverless-component@3.4.0-alpha.6
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:10
Top Results From Across the Web
Error deploying Mule application in mule standalone 3.5.0
You can check the java version in Anypoint Studio like below Go to--> Window-->Click on Preferences-->double click on java--> click on installed JREs....
Read more >Solved: When the Maven Deploy Plugin silently fails to deploy
At SnapLogic, we recently noticed that a particular build job that was responsible for deploying build artifacts to a Nexus repository via ...
Read more >Mule Maven Plugin fails during deploy/install with error
SYMPTOM. Mule Maven plugin fails after issuing a "mvn deploy" command with the following error:
Read more >Deployment Failure Cause Not Known for Exception creating ...
3.5. Attempts to deploy an application that uses it fail with: "Exception creating EntityManagerFactory using PersistenceProvider class org.
Read more >Build error : Failed to retrieve package sources #98 - GitHub
This error means that the package foreign has not been found during the deployment. 0.8-81 is the last CRAN version, so I am...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am getting the same error, and I am still on 3.4.0.
Oops, yeah I just checked and seems after moving the
sharp_node_modules
to core package, I was accidentally npmignoring those node_modules which are used for the image handler, so it didn’t get published to npm. Not sure why it didn’t fail locally, maybe it was cached somehow? Let me push a fix and deprecate 3.5.0…