Basic Node and Express - Serve JSON on a Specific Route

JavaScript
1

Hi Campers

I was just going through new curriculum and for some reason, this code is not going through for me on this challenge.

Challenge: https://learn.freecodecamp.org/apis-and-microservices/basic-node-and-express/serve-json-on-a-specific-route

Code that I have for this challenge

app.get(function(req, res, next) {
    console.log('Hello json');
    fs.readFile(__dirname + '/package.json', function(err, data) {
      if(err) return next(err);
      res.type('txt').send(data.toString());
    });
  });

Did I make some silly boo-boo that I am not noticing ?

Thanks for help in advance.

2

Updated code

app.get(function(req, res, next) {
    console.log('Hello json');
    fs.readFile('/package.json', function(err, data) {
      if(err) return next(err);
      res.type('txt').send(data.toString());
    });
  });

Still not working

Saying not found

3

@BoCode84 what is saying is not found?

4

@Mortuie

This is what I see

// running test
Not Found
// tests completed
5

@BoCode84 I see one error which is you havenā€™t specified a route.
i.e.

app.get('/json', function(req, res, next) {
    ........
}

I assume that is why it is saying not found as you havenā€™t specified a route to serve. Everything else seems fine!

6

I knew there was something :slight_smile: ā€¦ thanks.

Now itā€™s showing me different error

// running test
ENOENT: no such file or directory, open '/package.json'
// tests completed
1 Like
7

Still getting error ; anyone ?

8

Got it resolved!

Thanks everyone!

1 Like
9

Hello,

I am having a similar issue with this portion of the Node.js section. How were you able to configure the proper code?

10

i get stuck too bro.

11

can you tell me the solution

12

@Devilcode007 & @dhahn1

app.get('/json', (req, res) => {
  let message = 'Hello json'
  if (process.env.MESSAGE_STYLE === 'uppercase') {
    return res.json({"message": message.toUpperCase()})
  }
  return res.status(200).json({"message": message})
})

This is my solution ; you might have to check your whole code to see if this solution fits your code

1 Like
13

app.get(ā€™/jsonā€™,function(req,res)
{
let message=ā€œHello jsonā€;
res.status(200).setHeader(ā€˜Content-Typeā€™, ā€˜application/jsonā€™);

res.json({ā€œmessageā€: message});

});

14

if you use the Glitch, itā€™s very simple to pass the test as below.

QQ%E6%88%AA%E5%9B%BE20180801220406
QQ%E6%88%AA%E5%9B%BE20180801220406829Ɨ489 30.3 KB

2 Likes
15

Iā€™m getting no found here as hell, even if I can show the JSON response on the browser using the [glitch_url]/json. I assume is a testing problem as it works perfectly for me.

https://platinum-windscreen.glitch.me/json

app.get("/json", function(req, res) {
  let message = 'Hello json'
  if (process.env.MESSAGE_STYLE === 'uppercase') {
    return res.status(200).json({"message": message.toUpperCase()})
  }
  return res.status(200).json({"message": message})
})

.env file is

MESSAGE_STYLE="uppercase"
16

One must provide his/her app URL without ā€˜/jsonā€™ for passing the challenge i.e., in my case it is - https://outgoing-toast.glitch.me and not the URL of page where you are serving JSON response (https://outgoing-toast.glitch.me/json).

Hope it helps!

6 Likes
17

A simple answer to this challenge, similar to that of @ccrubby214 above:

app.get("/json", (req, res) => {
  res.json({"message": "Hello json"})
})
18

Iā€™m wondering if the tester isnā€™t working. I have tried all your guys solutions and have got nothing. I thought it maybe was the space after ā€œmessageā€: ā€œHello jsonā€ that was causing the issue but it is not. Please help:

https://axiomatic-athlete.glitch.me/json
https://axiomatic-athlete.glitch.me/

image
image671Ɨ501 56.7 KB

This is resolved. After going on to the next lesson, I was able to find deeper discussion on the same issue. This is what I used to solve this lesson:

app.use('/json', (req, res) => {
   let message = "Hello json"
   return res.json({"message": message})
})
2 Likes
19

@gauravano, YOU, my friend, had the answer which saved me from going [completely] bald!! I could have saved myself HOURS of frustration had I found your answer earlier. This worked for me. THANK YOU!! Youā€™re an absolute genius, kind sir :wink:

20

Thanks. Spent too long trying to ensure the test url fit the proposed and presumed URI for the testing. Doesnā€™t seem logical that the test should be at the root seeing that the instruction is proposing a reroute.

Perhaps FCC should clarify on the challenge page.