Firebase deployement of ; react-spw; Node.JS 14; mongoDB - mongodb

I am trying to host a React application on Firebase, but am having some issues. I have previous experience with Angular and Firebase, as well as some knowledge of different JavaScript interpreters and basic Firebase. I am currently working with Node.js 14 and React, and have been using Firebase tools that are compatible with this version of Node.js.
The issue I am facing is that after building my project with React, it creates a new folder for the build. I am not familiar with this process and am having difficulty understanding how to host my application on Firebase with this new folder structure.
(The basic; npm install -g firebase-tools, firebase login, firebase init, npm run build, firebase deploy. has not worked.)
I have searched for documentation on this issue and have tried looking for any dependency issues, but have not been able to resolve the problem. I would greatly appreciate any help or guidance on how to host my React application on Firebase. Thank you in advance.

Related

SAPUI5 Can't run local Fiori Application properly from VS Code

We used this tutorial to start developing Fiori apps with VS Code:
https://blogs.sap.com/2020/07/16/developing-sap-fiori-app-using-sap-fiori-tools-in-visual-studio-code/
Everything works fine so far, except the connection to the backend services. When we want to start the application locally we get the following error by getting the OData metadata.
Our server config in ui5-local.yaml:
Before switching to VS Code we used the local WebIDE which worked fine. So I guess there is no configuration on the SAP system which blocks the request.
Did anyone face the same issue and has a solution for us? I searched online and couldn't find anything that fits our problem.
Thanks a lot for any hints.
try this npm install ui5-middleware-proxy-basicauth --save-dev
Are you by any chance in corporate network which uses Self-Signed Certificate. If so npm might fail. Change the ignoreCertError: true and give it a try.

using Material-UI with create-react-app (react 16)

CRA now uses React 17 default and it is advised that we use an older version of CRA that uses R16 whilst MUI5 is being developed. Can someone advise me how they download an older version of CRA? I have tried npx create-react-app client --typescript --scripts-version react-scripts#3.4.4 and I get Error: Cannot find module 'cra-template'. I know this is strictly a CRA question but I thought someone that uses MUI might already have some experience with this problem.

How to connect the back end and the front end and use the Discovery API in IBM cloud app services?

I am very new to using APIs so please excuse me. I am currently using a Python-Django App service from IBM cloud app services and the IBM Watson Discovery resouce. I have followed all the steps given here:
https://console.bluemix.net/docs/apps/tutorials/tutorial_web.html#before-you-begin
I have a machine that has docker and so the app got built successfully. However I am lost as to how I am supposed to get the front end ( which I am writing in bootstrap, javascript ) to connect to the backend and link the API.
EDIT
For example : I want my app to accept documents, feed them in Discovery, extract the keywords and sentiments and display them in the UI. How do I know what to access from the server side code and what to link where in the UI.
It is a very broad question but its a compulsory project I need to do and I am clueless. Pleaassee Help !
Before you try to integrate an API, you will need to be familiar with Python and Django. If that is not the case, then you really need to go through a series of tutorials.
Then before deploying to the cloud, you will be better off running your Django app locally on your laptop. Use pip to install the watson-developer-cloud pypi module and use the API documentation to build the python code in your Django application - https://www.ibm.com/watson/developercloud/discovery/api/v1/python.html?python#query
If none of this makes sense, then you need to brush up on your knowledge of Python, Pip, and Django.
When you have the app running on your machine, then you will be ready to package it up into either a docker image or cloud foundry container and deploy to the cloud.

Unable to deploy using firebase 3.0.0

I'm trying to deploy using firebase 3.0.0 latest CLI version.
Unfortunately I get this errors:
Error: Unable to authorize access to project XXXX
Note: This version of the Firebase CLI is only compatible with projects upgraded
to the new Firebase Console. To access firebase.com apps, you will need to
use a previous version: npm install -g firebase-tools#^2.1
Any ideas?
As a matter of fact I was trying to deploy to a custom domain that was not yet verified.
My bad :(
Sorry guys.
I believe you need to upgrade your project to the new Firebase at firebase.google.com. If you haven't you should check out the announcements at Google I/O 2016.

Deploying Meteor + Angular2 app to Heroku

I have an app I'm writing using Meteor, Angular2 (using the angular-meteor package), Typescript, and MongoDB. I'm trying to put it up on Heroku and running into difficulties. I'm using this meteor buildpack. I'm not sure whether the problems are with Meteor, Heroku, or Angular2, though I suspect it's something Heroku isn't configuring correctly for Angular2. The site is at http://alfred-zahner.herokuapp.com/ and the error I'm getting is:
EXCEPTION: No provider for t! (e -> t)
I've checked the Heroku logs and there is no sign of trouble there. Part of my problem is that I can't see what t and e are, as someone (Heroku?) is uglifying the JavaScript. I'm not really sure how to proceed in debugging this.
One way to solve this problem would be to figure out and fix the error, but I'd be happy if there's a better build pack, or even a better (must be free!) hosting environment that I could be using.
Edit
It's not Heroku's problem. The same thing happens when deploying to Meteor's built in deployment testing (meteor deploy site.meteor.com). If I deploy using meteor deploy --debug site.meteor.com, however, it works, so Angular2 has some problem with the extra processing that happens when Meteor prepares an app for production.
On the angular2-meteor Github I found out that this is an issue with Angular 2 in particular, when using UglifyJS. For now, it seems the only solution is to use meteor deploy --debug. I'm planning to just use that on meteor's built in hosting until Angular 2 plays nicely.