Narendra

Hi, my name is Narendra, and I am from Hyderabad. I have around 3 years of experience in web development. In my experience, I have worked on building ecommerce platforms, and I've also worked on insurance portals, information displaying, and integrating payment systems to websites, among many other things. Coming to my skills, I have mostly worked on development within JavaScript, React, and Node.js. I have also used AWS services to build backend services. That's it.

This is the purpose of the package.json file in a Node.js application. So the purpose of the package.json file is to know about that project. So it tells you about the dependencies it needs for that project. Like, what type of packages you need to use in that project, which will be there in the package.json, and the name of the project, and how you want to control that project, meaning how you want to test that project or how you want to run that project. Those are the commands we can include in the package.json. And also you can include this, development dependencies and the dependencies. So the development dependencies are mainly used to run that project, but the dependencies, you actually use them in your code. The package.json is the main entry file for that project.

To engineer our Node.js API to be secured from common vulnerabilities, we will use some keys at our side, we can use the JWT tokens and also we can use the Cookies that can come from different end applications, we can use that. We can use a private key private mechanisms, I mean, it will come under the available tokens as well. So this type of mechanism, we can use to secure our APIs. And also, we can add, I mean, from which we can call this API. Like, only from this domain we can allow to make an API call. So these types of securities, we can provide in our API.

So function delete is there. Hello return message. So here, basically, we are calling a function by passing an argument to all. But in the function greet, we are not accepting any parameter. So if we add the parameter inside the greet function, then that will be it. It will work normally. Because we are calling a function with an argument, but we are not accepting any parameters in that function. So we have to accept that parameter and it will work as expected. So what we have to do is, we have to modify the function greet. Inside the function greet, we have to write a parameter, name.

We can use just and we can we have to just pass the props to that function normally. However, we have to work on writing unit test, by passing the props and parameters. We can test it, I guess. Corrected text: We can use Jest and we can pass the props to that function normally. However, we have to work on writing unit tests, by passing the props and parameters. We can test it.

Imagine you have an optimized in Node. Js application. Which profiling tools would you use? And how would you identify the bot index? So in order to Debug the Node. Js application, we can use Chrome debugger. And 2 profiling tools, I haven't used, any profiling tools to Optimize the Node JS application. But in order to optimize, we just need to analyze the code and, wherever is necessary, we can improve the performance by reviewing the code. that's how we can do it. And the tools, exactly, I don't know. We can Decrease we can redo maybe you can remove unnecessary packages. we can we are not using in our code. That way, we can optimize the Node JS application. Yeah. That's it. And, also, suppose if you are making any API calls And we have we can use the promise. And we can make parallel API calls using a promise.all. So in that way, we can optimize the Node. Js application. You can see.

Let's plan your process for troubleshooting and memory leaking Node. Js application that interacts Sweet external APIs. So how basically we can troubleshoot it? Once we make an API call to external API from the Node. Js application, We just need to come out of this, function. And, that gives a very large object, but we don't need that large object to be stored anywhere. And, we only want a few of the data from this external API, then we can create 1 object from that. And we just need to use that instead of using Everything that is coming from the external API. In that way, we can reduce some numerics.

Can you discuss a method for end to end testing in full stack application using Node. Js React. Same method for end to end testing in full stack application using Node and React. So in order to discuss, both the things, we have to manually test it. Sorry. I don't know exactly because, for testing, I haven't used any tools. So as of now, I just tested manually application. but, in order to testing, we can use the alerts. I mean, if something goes wrong in that survey I mean, API Node. Js API service. Then at that time, in the cache blocks, we can create alerts. I mean, this endpoint was failed. So that, and that we will integrate with the with it, with our any start application or anything where we can regularly check so that we'll get to know how many times it is failing. Like, that way, we can test it, our IP services and, everything in the Node. Js application.

What situation would you choose Redux for state management in React, and what are the alternatives? So the situation is, like, Redux is mainly for the state management and React for the larger applications. So suppose if there are multiple places in an application where you are using one API call. And in each API call, you have to show a loader. So suppose if you use Redux at that time, in the Redux state, you can actually place a loading property. Using that, you can actually show the loader immediately. Otherwise, what you have to do in every component is separately maintain the loading state for that API. Then, based on that, you have to write the logic. But if you have that Redux state, it will be applicable to the entire application. So in that way, you can manage it throughout your app. There are alternatives like you can use the Context API, which is provided by React that you can use it.

So when did you decide to use GraphQL over REST in the project and what are the implications for our Node.js application? So when can we use GraphQL instead of REST? I mean, suppose we have to make multiple API calls in a single API call? Let's say, there is a movies API. So in that, what we have to do so it will give us details about the movie, the director, and the hero's casting everyone? So also, suppose if we want to get something regarding any of the one hero's details, then we have to make separate API calls for that. It's the same for getting all the movies what he has done. We have to use one more API call for that. So in those situations, a GraphQL query will be useful instead of making multiple API calls. So queries will be executed directly on the database. So it's in those kinds of situations that we can choose GraphQL. And also, GraphQL will be useful whenever we don't need all the data from the API. We only need certain fields from that API. Let's say, we want only the movie name and we want only the director name and we want only the budget like that. But if we use the API, we will get all the details.

How did you incorporate automated build and deployment time frames into your real stack development workflows? So, I've used an external platform and ourselves. In GitHub, we have a way to add a workflow with commits, what we're doing for this project. Let's say, if you push any PR to the main branch, then at that time, you have to build and deploy to any AWS services or external deployment services you're using. Then we just need to provide the deployment URL. I mean, create a hook for that, and it will automatically trigger GitHub to do that for us. So, in GitHub, what we've done is create a YAML file in the workflow. So, in that way, it will work.

Can you discuss the time when you had to optimize content assets for better performance in a React application? You can use the crucial time when we have to optimize front-end assets for better performance. Yeah, in front-end assets, I mean, suppose if we have to load an image in a web application and it's taking more than 5 MB or 6 MB. So it will take time to download it. And to see it in the front end, it will take some time to render it onto the UI. So in order to do that, we can use some external platform that will optimize the images. So I can say in a Next.js application, we have an image tag. So that will optimize the image assets and images. So it will automatically reduce the size of the file. But the picture will be as it is, but it will just reduce the memory size of that picture. Yeah. I haven't used tools to optimize images. But one thing I can say is you can use lazy loading. So instead of downloading everything at a time, so whenever it will be easily loaded whenever we open the application.