I am facing issues with Firebase functions where the parameters received from Express.js routes are

Question

I am facing issues with Firebase functions where the parameters received from Express.js routes are

I am encountering an issue while trying to use firebase functions to host my expressjs webapp. For some reason, all get parameters appear to be undefined. Can anyone help me figure out what the problem might be?

    import functions= require("firebase-functions");
    import admin= require("firebase-admin");
    import express= require("express");
    import bodyParser= require("body-parser");
    const app: express.Application = express();
    admin.initializeApp();

    app.get("/getstory", async (req,resp)=>{
        try{
            const preferred_storyid=req.params.preferred_storyid;
            console.log(`preferred_storyid ${preferred_storyid}`) //logs preferred_storyid undefined. Why?
resp.send("ok");
        }catch (e) {
            resp.send(`erequest_story. ${e}`);
        }
    });
    
    const faststoryapi = functions.https.onRequest(app);
    module.exports={faststoryapi}

After writing the code above, I deploy it using the command:

firebase deploy --only functions

I then send a GET request using Postman and encounter issues. You can view the screenshot https://i.sstatic.net/YChGg.png

PS: Another problem I have noticed is that I am unable to have more than one route. For example, having more than one post endpoint results in the second one not being called. How do you guys work around this limitation?

typescript firebase express google-cloud-functions

Answer 1

Answer №1

If you want to achieve a similar result, consider the following code snippet:

...
app.get(async (req,resp) => { // no path needed
    try{
        const preferred_storyid=req.params.preferred_storyid;
        console.log(`preferred_storyid ${preferred_storyid}`) //displays preferred_storyid as undefined. Any idea why?
        resp.send("ok");
    } catch (e) {
        resp.send(`erequest_story. ${e}`);
    }
});

const faststoryapi = functions.https.onRequest(app);
module.exports={faststoryapi}

You can access your function through the URL:

https://us-central1-<project-id>.cloudfunctions.net/faststoryapi

. The endpoint for the API will match the name of your exported function.

When hosting an express app in cloud functions, use req.query for URL parameters.
In Express, req.params is utilized for paths like the one shown below:

Route path: /users/:userId/books/:bookId
Request URL: http://localhost:3000/users/34/books/8989
req.params: { "userId": "34", "bookId": "8989" }

Therefore, you should make use of req.query instead of req.params.
Refer to this response for additional information.

Answer 2

If you want to achieve a similar result, consider the following code snippet:

...
app.get(async (req,resp) => { // no path needed
    try{
        const preferred_storyid=req.params.preferred_storyid;
        console.log(`preferred_storyid ${preferred_storyid}`) //displays preferred_storyid as undefined. Any idea why?
        resp.send("ok");
    } catch (e) {
        resp.send(`erequest_story. ${e}`);
    }
});

const faststoryapi = functions.https.onRequest(app);
module.exports={faststoryapi}

You can access your function through the URL:

https://us-central1-<project-id>.cloudfunctions.net/faststoryapi

. The endpoint for the API will match the name of your exported function.

When hosting an express app in cloud functions, use req.query for URL parameters.
In Express, req.params is utilized for paths like the one shown below:

Route path: /users/:userId/books/:bookId
Request URL: http://localhost:3000/users/34/books/8989
req.params: { "userId": "34", "bookId": "8989" }

Therefore, you should make use of req.query instead of req.params.
Refer to this response for additional information.

Answer 3

Answer №2

Within Firebase Functions, the req and res objects function similarly to those in ExpressJS. To fetch query parameters, utilize req.query.xxxx, whereas req.params.xxxx is used for retrieving path parameters.

Answer 4

Within Firebase Functions, the req and res objects function similarly to those in ExpressJS. To fetch query parameters, utilize req.query.xxxx, whereas req.params.xxxx is used for retrieving path parameters.

I am facing issues with Firebase functions where the parameters received from Express.js routes are

Answer №1

Answer №2

Similar questions

An ongoing challenge with user authentication in Express.js and Passport.js using a dynamic IP server on no-ip.org: the authentication process keeps

How can Firebase and Ionic be used to customize the password reset template for sending verification emails and more?

Creating a Lambda function in CDK: A guide to configuring the Dockerfile and setting environment variables

Searching in MongoDB: Using a dynamic regular expression in $where clause

Sending SQL data to a Node.js module upon receiving a client request

Angular 4 with Universal: Implementing 404 Status Code in Header for /404 Page Component

React: Dealing with unsuccessful imports

Retrieving results from PostgreSQL database using pagination technique

Why does Angular routerlink display %20 before the id path?

Various types of generics within an object

Tips on excluding specific files in a folder while rendering with Express using `fs.readdir`

Utilizing the Next.js "Link" Element as a Personalized React Component Using Typescript

Managing DOM elements within a Vue 3 template using Typescript

Using `await` or `then` with a Promise object can lead to varying results

What are best practices for implementing JWT for authentication purposes?

Can you share the appropriate tsconfig.json configuration for a service worker implementation?

Transferring information from Node.js to HTML with the help of EJS template engine

Encountered a runtime error in NgRx 7.4.0: "Uncaught TypeError: ctor is not a

Stop the interval once the route is altered in Angular 2

Can you provide a guide on setting up and utilizing mathlive within NuxtJS?