Narendra

Hi. Myself, I'm Narendra, and I am from Hyderabad. And I have around 3 years of experience in the web development. So in my experience, I have worked on building the ecommerce Right? And, uh, insurance calls, information displaying, and integrating the payment system to the website, and many more things. And coming to my skills, uh, I mostly worked on the development within the JavaScript, React and Node. Js. And, also, I have used the AWS services to build the back end services back end services. Um, Yeah. That's it. Pretty much about

This is the purpose of package. Json file in the Node. Js application. So the purpose of package. Json file is to know about that project. So it will tells you about what are the dependencies it needed for that project. Like, what what type of packages you need to use in that project you are using in that project that will be there in the package. Json and the name of the project and how you want to it will control that project, means 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 dot JSON. And also you can include this, uh, development dependencies and the dependencies. So the development dependencies is mainly used to run that, uh, project, but the dependencies, you actually use it in your code. The package. Json is the main entry file for that project.

What steps could you take to engineer your Node. Js API are secured from common vulnerabilities? So to make our API secure, we will use some Keys at our side, uh, we we can use the JWT tokens and also we can use the Cookies that can come from different end application, 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, uh, I mean, from which we can call this API. Like, uh, only from this domain we can we can allow to make an API call. So these type of securities, we can provide in our

We're given the following codes. Like, that it looks like the code isn't behaving as expected because of the syntax. Can you spot the mistake and tell us how we will fix it? So function delete is there. Hello return message. So here, basically, we are calling a function by passing a 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 name, then that will be it will it will work normally. Because we are calling a function with an argument verb, but we are not accepting any parameters in that function grid. So we have to accept that parameter and it will work as it is. So what we have to do is we have to do function grid. Inside the bracket, we have to write name.

How do you approach writing unit tests for React components that have complex state management and side effects. So in order to write, uh, unit test for the React components, we can use just and we can we have to just pass the props to that function normally. Haven't must work on writing the unit test, but I think, uh, by passing the props, and parameters. We can test it, I guess.

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, uh, I haven't used, uh, any profiling tools to Optimize the Node JS application. But in order to optimize, we just need to analyze the code and, uh, wherever is necessary, Uh, we can improve the performance by reviewing the code. Uh, 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. Uh, 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 we can use the promise. And we 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, uh, function. And, uh, that gives a very large large object, but we don't need that large object to be stored anywhere. And, uh, we only want a few of the data from this external API, then we can create 1 object from that. And we 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, uh, both the things, we have to manually test it. Sorry. I don't know exactly because, uh, for testing, I haven't used any tools. So as of now, I just tested manually application. Uh, but, uh, 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, uh, and that we will integrate with the with it, uh, with our any start application or anything where we can regularly check so that we we'll get to know how many times it is failing. Like, that way, we can test it, uh, our our, uh, our IP services and, uh, 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, uh, there there is, uh, there are 2, uh, in many places, you are using 1 API call. Used. And in each API call, wherever you are making at that place, you have to slow loader. So suppose if you use a Redux at that time, used. So in the redux state, we can actually place, uh, loading property. Used. So using that, uh, we can actually show the loader immediately. Otherwise, what we have to do in every in everywhere, we have to separately maintained that loading state for that, uh, API in your separate components. Then, um, based on that, you have to write the logic. But if you have that Redux state, so it will be applicable to the entire application. So in that way, you can manage it through your entire app. Uh, there are alternatives like, uh, you can use this, context API. So which is provided by React that you can use it. Yeah. That is the one thing you can do.

So when did you decide to use GraphQLO REST in the project and what are the implications for your we are in Node JS application. So when we can use the GraphQL instead of rest I mean, suppose if there are multiple API calls, we have to make, uh, in a single API call? Let let's say, there is an movies API. So in that, what we have to do so it will give you the details about, the movie and the director and the heroes casting everyone? So and also, suppose if you want to get something like, uh, regarding that any of the one hero details, then you have to make separate API call for that. It? And you want to get 1 more API call to fetch all the movies what he has done. So you have to use 1 more API call in for that. So in those situations, graph graphQL query will be useful instead of making multiple API calls. So queries will be directly a, directly we'll make on the database. So it at that kind of situations, uh, we can choose the GraphQL. And also, GraphQL will be useful whenever you don't need all the data from the API. You only need certain fields from that, uh, API. Let's say, You want only movie name and you want only the director name and you want only a budget like that. But if you use the API, and you will get all the details

How you incorporated automated build and deployment time frames into your real stack development workflows? So for automated build, I have used, uh, an external platform and, ourselves. So in the GitHub, we have a way to add to add, uh, uh, workflow with, uh, commits, what we are doing for this, for the project. I mean, let's say, if you are pushing any PR to this main branch, then at that time, you have to build and deploy to any AWS services, plat, uh, any external deployment services you are using, then we just need to provide the deployment URL. I mean, create a book for that and then it will automatically GitHub will automatically do that, uh, for us. So in the GitHub, what we have done is we have to create a, yep, IML files in the GitHub workflow. So in that way, it will work.

Can you discuss time when you had to optimize content assets for better performance in React application. Can use crucial time when we have to optimize front end assets for better performance. Yeah. In the front end assets, I mean, suppose if we have to load an image in the web application and it is taking and it has 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, uh, some time to render it onto the UI. So in order to do that, uh, we we can use some external platform that will optimize the images. So I can say in the in the Next. Js application, we have an image tag. So that will optimize the image assets and, uh, like, images. So it will automatically reduce this, uh, size of the file. And but the picture picture will be as it is, but it will just reduce the, uh, memory side of that picture. Yeah. I haven't used tools to optimize the images. Uh, but one thing I can say is you can use the loose lazy loading. So instead of downloading everything at a time so whenever it will be easily loaded whenever we open