im trying to deploy my project to vercel using vercel deploy--prebuilt however, i keep getting faced with the below error.1
I've checked the path which it says is missing but i think it can be seen in the below image? Can anyone advise on how to deal with this?
2 Project runs fine locally and vercel build runs smoothly and produces the file shown in image 1.
Related
I built a PWA and it works/installs fine when in development, but when in production I can't install it and this error comes up in dev tools screenshot of dev tools error, how can I fix it?
My App is hosted on netlify.
I tried putting my service worker files in the root directory as I kept seeing that come up in my long search for a solution but that didn't fix it
I built small project in Nextjs with react-bootstrap framework. My project working fine on local. I upload project on GitHub and connected to vercel. Now vercel showing below error
Module not found: Can't resolve 'react-bootstrap/Container' in '/vercel/path0/components/layout' because "react-bootstrap" is a module which is not available on "GitHub nor vercel".
Please help me on this.
Please find screenshot for reference
My firebase hosting deployments have suddenly started failing both in my Github CI Workflows and from my local machine.
$ firebase deploy --only hosting
=== Deploying to '<project>'...
i deploying hosting
Error: Failed to list functions for <project>
The project in question does not have any functions, and only hosts a static site. Google searches for "Failed to list functions" turn up empty, it seems like not a common problem. The only leads I can find indicate some kind of network error.
I have updated my firebase-tools, logged out and in again to generate a new CI token, tried the process from my Github workflows and also manually from my machine, all to the same effect.
I can't find any information about this problem, except that the error seems to come from this part of the firebase-tools codebase:
https://github.com/firebase/firebase-tools/blob/c0f19a32845135108c75a1050024965cb1e3f52d/src/gcp/cloudfunctions.ts
My firebase tools version was 11.14.0. I changed that to 11.13.0. Installed this specific version through npm install -g firebase-tools#11.13.0. After that I could successfully deploy.
I came across the issue. using firebase-tools version 10.5 or upgrading it to blaze plan fixed my issue
For various reasons we have decided to try to sidestep the slug-compilation and build our own slug locally to deploy through the API (as described here: https://devcenter.heroku.com/articles/platform-api-deploying-slugs).
The slug is built mostly like the java/scala buildpack using that buildpack jvm and is then combined with our play framework application dist file. Looking at the app dir of a normal/git-deployed app it looks aboutish the same.
Now, after deploying the slug through the api we get the expected dynos listed in the config page but the app crashes right away without giving any further information. Trying to attach a bash shell through heroku run bash it just times out.
Is there any way to get more information about why the app crashed out of heroku?
Ok, after some help from heroku support we figured out the following:
The slug tar files must be created so that the paths start with './' regular relative paths doesn't cut it. When we had that figured out we didn't really have any more big problems and now we have got a working alternative build and deploy to heroku pipeline that allows us to build or app locally and then deploy that.
I have to Work with WorkerRole project to deploy some services to perform the data sync with the other databses. i tried to publish but stuck, Internalization, Starting, Preparing, Recovering and finally aborted.
After getting the above stituation i build a simple workerrole project and tried to upload the result is same.
And i am not able to find out the problem with the same.
Please provide some help.
A typical problem, when deploying, is having a connection string pointing to the local emulated storage. This is the first thing I'd check if the worker role code runs locally in the emulator but fails when being published to Windows Azure.