subhro) where you want to create the … Some quick tips: Package name: remember to use kebab-case as this is the convention in the npm community. After you've finished the process of initializing your project using the Node Package Manager, node.js created a package.jsonfile in your project's root direcotry similar to this one: Initialize Composer on an existing Project, Initialize Database Versioning on a new project, Initialize Database Versioning on an existing project. license: The package’s license identifier (in Software Package Data Exchange (SPDX) format)– available licenses include Apache2.0, MIT, or ISC (the default), to name a few. In package.json file, you can look at scripts and dev-dependencies but the interesting part is the main property along with unpkge and browser. This tool will help you to create a new package.json asking you for the basic data needed. Using npm init to Initialize a Project. This still automatically rebuilds as files change and supports hot module replacement, but doesn't start a web server. If you link your main JavaScript file in the HTML using a relative path, Parcel will also process it for you, and replace the reference with a URL to the output file. In order to create such tool, we have to create and publish a project, our Cli itself, which contains an index.js and execute a main function when called. This command will ask you some questions to generate a package.json file in your project route that describes all the dependencies of your project. The aim of this guide is to get people getting started with Node.js and npm, while also showing some of the handy commands I use to bootstrap my projects. Sophisticated Package Search. npm init -y npm install --save-dev electron Electron (main) entry point ... We’ll create a single entry point for our electron main process, add a loader for all *.ts files to pass through the TypeScript compiler, and tell Webpack to dump the output alongside the source files. Interactively creates or updates a package.json file. Next, create an index.html and index.js file. cd !$ Tell git to make a repo. See `npm help init` for definitive documentation on these fields and exactly what they do. PS E:\tutorial-bot> npm init This utility will walk you through creating a package.json file. Here are the answers you should provide: package name: (barebones-npm-package) [Just Press Enter] version: (1.0.0) [Just Press Enter] description: A barebones npm package [Press Enter] entry point: (index.js) dist/index.js [Press Enter] test command: [Just Press Enter] If hot module replacement isn't working you may need to configure your editor. The package.json file identifies a project, who authored it and which file is the entry point. A dependency is loaded in two phases 1) the right directory is looked up and 2) the entry point within that directory is located. See the Production section for more details. const gfgFns = {} The object that is exported for others to use. Entry point will default to index.js. Parcel has a development server built in, which will automatically rebuild your app as you change files and supports hot module replacement for fast development. At this point npm init will ask you a few questions. The generated directory contains a bunch of folders. The src directory contains .vue file for development and entry.js file is the entry point for the bundler. npm init -y Parcel can take any type of file as an entry point, but an HTML or JavaScript file is a good place to start. NB: Parcel converts JS assets to ES5, which won't run in in the context of a