{"componentChunkName":"component---src-pages-author-author-yaml-id-js","path":"/author/hridayesh-sharma/","result":{"data":{"allMarkdownRemark":{"edges":[{"node":{"id":"8e68c6e7-ed5d-572e-85a0-732fe793dd49","html":"

Introduction

\n

In this blog, I will show you how to create a NodeJS server using core http module. We will create a simple server that will serve static assets and a simple API to return some JSON data.

\n

In the process, you will also learn about the request and response objects provided by NodeJS, which are used by every other framework built on top of NodeJS like ExpressJS etc.

\n

Prerequisites

\n
    \n
  1. NodeJS installed on your system. Download from Here
    2. \n
  2. A basic understanding of JavaScript
    3. \n
\n

With that in mind, let's begin.

\n

Step 1: Initialize the project

\n\n

Step 2: Add some static content

\n\n

Now we will create a node server that will serve our index.html file when a request is sent to /.

\n

server.js

\n
  const http = require('http');\n  const path = require('path');\n  const fs = require('fs');\n  const PORT = 3000;\n  const hostname = 'localhost';\n\n  // createServer is the http method used to create a web server that takes a callback.\n  const server = http.createServer(serverHandler);\n\n  // callback function definition\n  function serverHandler(req, res) => {\n    if(req.method === 'GET' && req.url === '/') {\n      let filePath = path.resolve(__dirname, 'public/index.html')\n      let fileExists = fs.existsSync(filePath);\n      if (!fileExists) {\n        res.statusCode = 404;\n        res.setHeader('Content-Type', 'text/html');\n        res.end(`\n          <html>\n            <body>\n              <h3>Page not found</h3>\n            </body>\n          </html>`)\n      } else {\n        res.statusCode = 200;\n        res.setHeader('Content-Type', 'text/html');\n        fs.createReadStream(filePath).pipe(res);\n      }\n    }\n  }\n\n  server.listen(PORT, hostname, () => {\n    console.log(`Server running at ${hostname}:${PORT}`);   \n  })
\n

Let's understand what just happened in the above code snippet:

\n\n

Now it's time to test our server. Run node server.js at the root of the project, and you will see the server running on PORT 3000.\nOpen your browser and enter localhost:3000 in the address bar, and you will get the HTML response.

\n

Step 4: Add a basic API to return some JSON data

\n

Now we will expand our callback, which we passed to createServer to handle one more GET request at /notes, which will return an array of notes to the browser.

\n

Update the serverHandler function with the following code snippet in your server.js file

\n

server.js

\n
  ...\n    function serverHandler(req, res) {\n      if(req.method === 'GET' && req.url === '/') {\n        let filePath = path.resolve(__dirname, 'public/index.html')\n        let fileExists = fs.existsSync(filePath);\n        if (!fileExists) {\n          res.statusCode = 404;\n          res.setHeader('Content-Type', 'text/html');\n          res.end(`\n            <html>\n              <body>\n                <h3>Page not found</h3>\n              </body>\n            </html>`)\n        } else {\n          res.statusCode = 200;\n          res.setHeader('Content-Type', 'text/html');\n          fs.createReadStream(filePath).pipe(res);\n        }\n      }\n      // Newly added code \n      if (req.method === 'GET' && req.url === "/notes") {\n        const notes = [\n          {\n            id: 1,\n            title: "Demo Note"\n          },\n          {\n            id: 2,\n            title: "Another Note"\n          }\n        ]\n\n        res.statusCode = 200;\n        res.setHeader('Content-Type', 'application/json');\n        res.end(JSON.stringify(notes));\n      } else {\n        res.setHeader('Content-Type', 'application/json')\n        res.end(JSON.stringify({message: `${req.method} is not supported for ${req.url}`}))\n      } \n  }\n  ...
\n\n

With that, we have created a simple node server to serve static content as well a simple API to return JSON data.

\n

Conclusion

\n

We saw how we had to handle each request with its method and the URL. With an increasing number of routes, such things become hard to manage as we will have to add multiple if statements. And that's why frameworks like ExpressJS, HapiJS exist, which makes creating servers in NodeJS very easy. But it's important to know what happens under the hood as there is no magic happening in those frameworks.

\n

The complete code for this blog can be found at Github Repo.

\n","frontmatter":{"title":"NodeJS Server using Core HTTP Module","author":{"id":"Hridayesh Sharma","github":"vyasriday","avatar":null},"date":"November 27, 2020","updated_date":null,"tags":["NodeJs","JavaScript"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/8d8c41d9ba7fce1f1b5c6d72e0982463/58556/coverImage.webp","srcSet":"/static/8d8c41d9ba7fce1f1b5c6d72e0982463/61e93/coverImage.webp 200w,\n/static/8d8c41d9ba7fce1f1b5c6d72e0982463/1f5c5/coverImage.webp 400w,\n/static/8d8c41d9ba7fce1f1b5c6d72e0982463/58556/coverImage.webp 800w,\n/static/8d8c41d9ba7fce1f1b5c6d72e0982463/99238/coverImage.webp 1200w","sizes":"(max-width: 800px) 100vw, 800px"}}}},"fields":{"authorId":"Hridayesh Sharma","slug":"/engineering/node-http-module-server/"}}},{"node":{"id":"b6a8ce3e-1926-5347-9eca-401383cd7d81","html":"

LoginRadius Open Source Projects

\n

Just 1 week left in hacktoberfest 2020 and being part of it, we at LoginRadius are all set with lots of our projects going open source this year.

\n
\n

To get LoginRadius swags see our Hacktoberfest Launch Blog. We have around 500 swags for our open source contributors.

\n
\n

Here is a list of our open source projects available on Github for hacktoberfest 2020

\n

\"loginradius-hacktoberfest\"

\n\n
\n

Check the open issues on each of the projects as well as Pull Request before creating a new one. Happy Coding!\nStay tuned for more updates from LoginRadius and don't forget to check our Hacktoberfest Page to get around 500 swags from LoginRadius.

\n
\n","frontmatter":{"title":"LoginRadius Open Source For Hacktoberfest 2020","author":{"id":"Hridayesh Sharma","github":"vyasriday","avatar":null},"date":"September 25, 2020","updated_date":null,"tags":["hacktoberfest","open-source","LoginRadius"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5873015873015872,"src":"/static/9a2056972f92077b2af8b32ecc2fcbdd/58556/hacktober-fest-banner.webp","srcSet":"/static/9a2056972f92077b2af8b32ecc2fcbdd/61e93/hacktober-fest-banner.webp 200w,\n/static/9a2056972f92077b2af8b32ecc2fcbdd/1f5c5/hacktober-fest-banner.webp 400w,\n/static/9a2056972f92077b2af8b32ecc2fcbdd/58556/hacktober-fest-banner.webp 800w,\n/static/9a2056972f92077b2af8b32ecc2fcbdd/e30b5/hacktober-fest-banner.webp 1000w","sizes":"(max-width: 800px) 100vw, 800px"}}}},"fields":{"authorId":"Hridayesh Sharma","slug":"/engineering/loginradius-opensource-repos-for-hacktoberfest-2020/"}}},{"node":{"id":"10f69e88-7a32-500a-a160-d143cba1f47b","html":"

Have you ever thought about what the world would be like if open-source didn't exist?

\n

It's hard to imagine a world without open source these days. Open source powers the biggest organizations of today's world. Open-source software like Linux runs most of today's servers and also powers the Android Operating System.

\n

Introducing Hacktoberfest 2020

\n

In a gist hacktoberfest is a festival of \"giving back to the community\".

\n

Hacktoberfest is a month-long celebration of open-source software in October month run by DigitalOcean in partnership with GitHub and DEV. Hacktoberfest is open to everyone in our global community!

\n

From Official Website:

\n
\n

Hacktoberfest is open to everyone in our global community. Whether you’re new to development, a student, long-time contributor, event host, or company of any size, you can help drive the growth of open source and make positive contributions to an ever-growing community. All backgrounds and skill levels are encouraged to complete the challenge.

\n
\n

The purpose of this month-long celebration is to get people started in open source and give back to the open-source community.

\n

It is the easiest way to get into open source for people who have never contributed to open-source community or find it difficult to contribute.

\n

How to contribute to Hacktoberfest?

\n

Anyone can contribute to hacktoberfest by registering at hacktoberfest website anytime between 1st October to 31st October.

\n

During this time, anyone who wishes to be part of this month-long fest needs to open four quality pull requests on any of the open-source projects on Github.

\n

How to find Projects?

\n

Finding projects can be a bit challenging. It can be the tools you are already using, or different tools can be used to find the issues based on various labels. Tools like issuehub are really helpful for the same.

\n

This year LoginRadius is going to be part of Hacktoberfest by open-sourcing a lot of its projects and accepting contributions on them including its Engineering Blog.

\n

Getting LoginRadius branded swags

\n

Like I said, this year LoginRadius will be part of hacktoberfest and yes, we are here with some cool swags. We have got around 500 t-shirts for people contributing to our open source repositories. We will soon share details on how to get LoginRadius swags as well as our open source repositories on our Blog.

\n

Stay tuned and don’t forget to mention your open-source projects for us to contribute.

\n","frontmatter":{"title":"LoginRadius Supports Hacktoberfest 2020","author":{"id":"Hridayesh Sharma","github":"vyasriday","avatar":null},"date":"September 18, 2020","updated_date":null,"tags":["hacktoberfest","open-source","LoginRadius"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5873015873015872,"src":"/static/9a2056972f92077b2af8b32ecc2fcbdd/58556/hacktober-fest-banner.webp","srcSet":"/static/9a2056972f92077b2af8b32ecc2fcbdd/61e93/hacktober-fest-banner.webp 200w,\n/static/9a2056972f92077b2af8b32ecc2fcbdd/1f5c5/hacktober-fest-banner.webp 400w,\n/static/9a2056972f92077b2af8b32ecc2fcbdd/58556/hacktober-fest-banner.webp 800w,\n/static/9a2056972f92077b2af8b32ecc2fcbdd/e30b5/hacktober-fest-banner.webp 1000w","sizes":"(max-width: 800px) 100vw, 800px"}}}},"fields":{"authorId":"Hridayesh Sharma","slug":"/engineering/loginradius-supports-hacktoberfest-2020/"}}},{"node":{"id":"62fbde41-4351-55bd-b987-f04716189d87","html":"

In JavaScript, web workers allow developers to benefit from parallel programming. Parallel programming enables various computations to be performed at the same time by applications. It is helpful to consider the importance of web staff as an example of how humans benefit from parallel tasks.

\n

Web workers give us the ability to write multi-threaded Javascript that doesn't block the DOM. To some extent, even asynchronous operations block the DOM. On the other hand, Web employees help us solve this problem, escape from the single-threaded world, and achieve higher performance on our web pages.

\n

What are web workers in JS?

\n

Web Workers are a simple means of running scripts in background threads for web content. Without interfering with the user interface, the worker thread may perform tasks.

\n

Furthermore, they can use XMLHttpRequest to perform I/O (although the responseXML and channel attributes are always null) or fetch (with no such restrictions). Once created, by posting messages to an event handler defined by that code, a worker can send messages to the JavaScript code that made it (and vice versa).

\n

Why Use JavaScript Web Workers?

\n

Web workers let you build background threads separate from the main execution thread, where the logic of the user interface is usually executed.

\n

The key benefit of this separation of workload is that inside an isolated thread and without interrupting or impacting the main thread's responsiveness and usability, you can perform costly operations.

\n

When the background thread completes its mission, the main thread is informed of the results seamlessly via an event handled by standard JavaScript event handling.

\n

Setting Up Web Workers & Multi-threading to JavaScript

\n

Step 1: Create a project folder and add index.html in the root of it.

\n
<!DOCTYPE html>\n<html lang="en">\n  <head>\n    <meta charset="UTF-8" />\n    <meta name="viewport" content="width=device-width, initial-scale=1.0" />\n    <title>Club JavaScripters</title>\n  </head>\n  <body>\n    <button>Can you click me?</button>\n    <h2>Let's do the party. πŸ‘―β€β™‚οΈβ€</h2>\n    <ul id="club"></ul>\n    <script src="./main.js"></script>\n  </body>\n</html>
\n

We just created a simple HTML page with a link to our javascript file which we will create in a moment.

\n

Step 2: Let's add our JavaScript code in two separate files, main.js and worker.js in the same folder.

\n

main.js

\n
const persons = [\n  {\n    name: "Hriday",\n    isMember: true,\n  },\n  {\n    name: "Hridayesh",\n    isMember: false,\n  },\n  {\n    name: "Bob",\n    isMember: true,\n  },\n  {\n    name: "Daisy",\n    isMember: true,\n  },\n]\n\n// Our club container\nconst club = document.getElementById("club")\nlet worker\n\n/**\n * Function entry allows entry to people coming to our club\n */\nfunction entry(persons) {\n  persons.forEach(person => {\n    const { isMember, name } = person\n    const listItem = document.createElement("li")\n    listItem.textContent = name\n    // if a person is not registered, register them first\n    if (!isMember) {\n      // create a new worker thread\n      worker = new Worker("worker.js")\n      // pass data to worker thread\n      worker.postMessage(name)\n      // listen to any data passed from worker thread\n      worker.addEventListener("message", event => {\n        if (event.data) {\n          club.appendChild(listItem)\n        }\n      })\n    } else {\n      // if they are registered let them in\n      club.appendChild(listItem)\n    }\n  })\n}\n\nentry(persons)
\n

worker.js

\n
// addEventListener is directly accessible in worker file\naddEventListener("message", event => {\n  // extract person passed from main thread from event object\n  let person = event.data\n  registerMember(person)\n})\n\nfunction registerMember(member) {\n  // generating membership card takes some amount of time\n  let i = 0\n  while (i < Math.pow(10, 10)) {\n    i++\n  }\n  // send result back to the main thread\n  postMessage(true)\n  close()\n}
\n

Step 3: On to some Explanations about what just happened.

\n

Now, the problem I faced when I went to the club with Hriday was that I (and everyone else after me) had to wait for my registration process to complete. We don't want that to happen to our virtual club and therefore we added one more person (thread) who is in charge of the whole registration process. Once registration is done, he will tell the main guy(thread) to let the new person in.

\n

Here's what we did to solve it in our code.

\n
    \n
  1. First of all we check for each person if they are a member or not. If they are, we let them in.
    2. \n
  2. If someone is not a member of the club yet, we create a worker thread for it using new Worker('path to worker code') and pass that person to the worker thread using worker.postMessage() and add the person as a member after registering them.
    3. \n
  3. To simulate the registration process we are doing some processing using a long while loop. In real life this could be some cryptographic code, image processing or anything that is CPU intensive and might block the main thread and make the page unresponsive.
    4. \n
  4. Once registered, the worker thread let's the main thread know about it by sending data using postMessage and the main thread listens for it using onmessage handler and lets the person in the club i.e add to DOM.
    5. \n
  5. Once we get the result from the worker thread, we close it using close().
    6. \n
\n

Web Workers FAQs

\n

How do the main thread and worker threads talk to each other?

\n

They talk to each other by message passing. Both workers and the main thread use postMessage to send data to each other and onmessage event handler to get data. The data is available inside the event's data property.\nYou can only pass one argument to postMessage. If you wish to pass multiple arguments use an object instead.

\n

Can I update DOM in a worker thread or access window object?

\n

No you can not update DOM in a worker thread as worker threads run in a separate context from the main window and don't have access to window object and document object but they do have access to some of the window object's capabilities like Websockets and indexedDB.

\n

Why did you add worker code in a separate file?

\n

It's important that the worker code must be in a separate file, which we can use to create a separate worker thread by using the Worker constructor and passing it the path of the file.

\n

Why did you add that button? I can easily click it.

\n

You were able to click that button because we did not block the main thread.\nTo see the difference add the following code to main.js and see the difference.

\n
const persons = [\n  {\n    name: "Joe",\n    isMember: true,\n  },\n  {\n    name: "Hriday",\n    isMember: true,\n  },\n  {\n    name: "Hridayesh",\n    isMember: false,\n  },\n  {\n    name: "Bob",\n    isMember: true,\n  },\n  {\n    name: "Daisy",\n    isMember: true,\n  },\n]\n\n// Our club container\nconst club = document.getElementById("club")\nlet worker\n\nfunction entry() {\n  persons.forEach(person => {\n    const { isMember, name } = person\n    const listItem = document.createElement("li")\n    listItem.textContent = name\n    if (!isMember) {\n      let memeberAdded = registerMember(person)\n      if (memeberAdded) club.appendChild(listItem)\n    } else {\n      club.appendChild(listItem)\n    }\n  })\n}\n\nentry()\n\nfunction registerMember(member) {\n  let i = 0\n  while (i < Math.pow(10, 10)) {\n    i++\n  }\n  return true\n  close()\n}
\n

Could you still click the button?

\n

You can share that answer in the comment section πŸ˜‰ To get the full code you can visit to Github Repo

\n

Conclusion

\n

We introduced web workers in this article, a technology that helps the web industry keep up with demanding web applications. This is achieved by providing web apps with a way to exploit multiprocessor and multi-threaded machines by granting JavaScript some multi-threaded superpowers.

\n

Do you have any tips on web workers and the web as a forum for programming? Let us know in the comment section below.

\n","frontmatter":{"title":"Web Workers: How to add multi-threading in JS","author":{"id":"Hridayesh Sharma","github":"vyasriday","avatar":null},"date":"September 09, 2020","updated_date":null,"tags":["JavaScript","Web"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/2e0bb83a49cc5eb5b04a62c51cf495bb/58556/cover.webp","srcSet":"/static/2e0bb83a49cc5eb5b04a62c51cf495bb/61e93/cover.webp 200w,\n/static/2e0bb83a49cc5eb5b04a62c51cf495bb/1f5c5/cover.webp 400w,\n/static/2e0bb83a49cc5eb5b04a62c51cf495bb/58556/cover.webp 800w,\n/static/2e0bb83a49cc5eb5b04a62c51cf495bb/99238/cover.webp 1200w,\n/static/2e0bb83a49cc5eb5b04a62c51cf495bb/135cd/cover.webp 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}}},"fields":{"authorId":"Hridayesh Sharma","slug":"/engineering/adding-multi-threading-to-javascript-using-web-workers/"}}},{"node":{"id":"318b721d-715f-5359-84fd-a36ffc2b699f","html":"

In this blog we will learn how to create our own webpack configuration to bundle a small JavaScript utility library using webpack and babel.

\n

This blog will be divided into two parts:

\n\n

Let's create the source code for our library. For that we will be create two utility functions into two separate files in our source folder.

\n

Step 1 : Create a directory demo and run following command in it.

\n
  $ npm init -y
\n

The above command will create a package.json in your project root. I am using a --y to initialize it with default options.

\n

Directory Structure

\n
demo\n  |-- src/\n  |-- package.json
\n

Step 2: Adding our source code.

\n

Let's add our source code into src directory:

\n
src\n |--index.js\n |--capital.js\n |--addDOMContent.js
\n

Our utility library contains two functions capital, to capitalize a string and addDOMContent, to add content to a web page, each in it's own module.

\n

capital.js

\n
function capital(string) {\n  const capitalizedString =\n    string.substring(0, 1).toUpperCase() + string.substring(1)\n  return capitalizedString\n}\n\nexport default capital
\n

addDOMContent.js

\n
function addDOMContent(content) {\n  const node = document.createElement("h1")\n  node.innerText = content\n  document.body.appendChild(node)\n}\n\nexport default addDOMContent
\n

Inside our index.js, we will import these two functions.

\n

index.js

\n
import capital from "./capital"\nimport addDOMContent from "./addDOMContent"\n\nexport { capital, addDOMContent }
\n

So far we got the source code ready but we still need to bundle it so that the browsers can understand and oh boy!, we need to support some older browsers too πŸ™„. Anyway, being responsible developers we are going to do that 😎.

\n

Step 3: Let's install some of our project dev dependencies as they are only needed during development.

\n
 $ npm i --save-dev webpack webpack-cli @babel/core @babel/preset-env babel-loader
\n

We need webpack to bundle our code and webpack-cli is a command-line tool that uses webpack to do the same. Also webpack requires babel-loader to transpile our ES6 code to ES5 before bundling (Remember, what I said about being responsible developers πŸ˜ƒ).

\n

Step 4: Now let's get our webpack and babel configuration in place. (We are almost there)

\n

4.1. Create a webpack.config.js at the root of the project.

\n

webpack.config.js

\n
const path = require("path")\n\nmodule.exports = {\n  entry: path.resolve(__dirname, "src/index.js"),\n  output: {\n    path: path.resolve(__dirname, "dist"),\n    filename: "index_bundle.js",\n    library: "$",\n    libraryTarget: "umd",\n  },\n  module: {\n    rules: [\n      {\n        test: /\\.(js)$/,\n        exclude: /node_modules/,\n        use: "babel-loader",\n      },\n    ],\n  },\n  mode: "development",\n}
\n

There are a couple of things we need to understand about webpack configuration. Stay with me for a couple more minutes.

\n\n

.babelrc

\n
{\n  presets: ["@babel/preset-env"]\n}
\n

@babel/preset-env let's us use the latest Javascript without any polyfills and syntax transforms.babel-loader uses babel under the hood.

\n

By Now our Project Structure should look like this:

\n
demo\n|-- src\n|   |-- index.js\n|   |-- capital.js\n|   |-- addDOMContent.js\n|-- webpack.config.js\n|-- .babelrc\n|-- package.json\n|-- node_modules
\n

Step 5: One last step. I know I keep saying that but I promise this is last 😬.

\n

We have added our source files, now let's add an npm script to build final code using webpack and modify the main property inside our package.json to point it to our bundled code.

\n

package.json

\n
{\n  "name": "demo",\n  "version": "1.0.0",\n  "description": "",\n+  "main": "dist/index_bundle.js",\n+  "scripts": {\n+    "build": "webpack"\n+  },\n  "keywords": [],\n  "author": "Hridayesh Sharma",\n  "license": "ISC",\n  "dependencies": {},\n  "devDependencies": {\n    "@babel/core": "^7.10.4",\n    "@babel/preset-env": "^7.11.0",\n    "babel-loader": "^8.1.0",\n    "webpack": "^4.44.1",\n    "webpack-cli": "^3.3.12",\n  }\n}
\n

In package.json the main property is a direction to the entry point of the module that the package.json is describing.

\n

Hurray! We have finally created our utility library using ES6.πŸ₯³

\n

Run $npm run build to generate the bundled code and use it in the next step.

\n

Let's test our library now.

\n

index.html

\n
<!DOCTYPE html>\n<html lang="en">\n  <head>\n    <meta charset="UTF-8" />\n    <meta name="viewport" content="width=device-width, initial-scale=1.0" />\n    <title>Demo</title>\n  </head>\n  <body>\n    <script src="dist/index_bundle.js"></script>\n    <script>\n      console.log($)\n      alert($.capital("hridayesh"))\n      $.addDOMContent("Well It Works Fine!!!")\n    </script>\n  </body>\n</html>
\n

Save it and run it in your browser. You will see the name capitalized.

\n

The complete code is available at LoginRadius Engineering Blog Sample Repo

\n

Thanks for reading the blog. For detailed information and execution example of this blog, please refer to the video below:

\n\n","frontmatter":{"title":"Let's Write a JavaScript Library in ES6 using Webpack and Babel","author":{"id":"Hridayesh Sharma","github":"vyasriday","avatar":null},"date":"August 18, 2020","updated_date":null,"tags":["JavaScript","Webpack","NodeJs"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/b9b74a766ec8c0c06733b438fefae5ae/58556/cover.webp","srcSet":"/static/b9b74a766ec8c0c06733b438fefae5ae/61e93/cover.webp 200w,\n/static/b9b74a766ec8c0c06733b438fefae5ae/1f5c5/cover.webp 400w,\n/static/b9b74a766ec8c0c06733b438fefae5ae/58556/cover.webp 800w,\n/static/b9b74a766ec8c0c06733b438fefae5ae/cc834/cover.webp 1024w","sizes":"(max-width: 800px) 100vw, 800px"}}}},"fields":{"authorId":"Hridayesh Sharma","slug":"/engineering/write-a-javascript-library-using-webpack-and-babel/"}}}]},"authorYaml":{"id":"Hridayesh Sharma","bio":"Hridayesh Sharma is a Software Engineer at LoginRadius who is interested in how the web works and developer tools that make working with web easier.","github":"vyasriday","stackoverflow":"6235787","linkedin":"hridayesh-sharma","medium":null,"twitter":"vyasriday","avatar":null}},"pageContext":{"id":"Hridayesh Sharma","__params":{"id":"hridayesh-sharma"}}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}