⬡ webpack: assets by status 0 bytes 1 asset Most aren't used in this project, but it's good to know that this tool is packed with functionality if nothing else. Type node_modules/.bin/wp to run the locally installed webpack-nano.Īfter running, you should see a version, a link to the command line interface guide and an extensive list of options. It's used in the book as it aligns well with Yarn and yarn add. Webpack-cli comes with additional functionality, including init and migrate commands that allow you to create new webpack configuration fast and update from an older version to a newer one. We're using webpack-nano over the official webpack-cli as it has enough features for the book project while being directly compatible with webpack 4 and 5. In addition to installing the package locally below the node_modules directory, npm also generates an entry for the executable in the node_modules/.bin directory. You should see webpack and webpack-nano in your package.json devDependencies section after this. To add webpack to the project, run: npm add webpack webpack-nano -develop # -develop = -D The approach works nicely with Continuous Integration (CI) setups as well: a CI system can install project's local dependencies, compile the project using them, and then push the result to a server. Installing webpack #Įven though webpack can be installed globally ( npm add webpack -g), it's a good idea to maintain it as a dependency of your project to avoid issues, as then you have control over the exact version you are running. You can create a commit per step and tag per chapter, so it's easier to move back and forth if you want. This is an excellent chance to set up version control using Git. The official documentation explains package.json options in more detail. You can tweak the generated package.json manually to make further changes to it even though a part of the operations modify the file automatically for you. # -y generates a `package.json` with default values # Set the defaults at ~/.npmrc npm init -y
To get a starting point, create a directory for the project, and set up a package.json there as npm uses that to manage project dependencies. The completed configuration is available at GitHub for reference. To get a more controlled environment, use Docker, nvm, or a similar tool. You should have node and npm (or yarn) commands available at your terminal. You should use at least the most current LTS (long-term support) version as the configuration of the book has been written with modern Node features in mind. Before getting started, make sure you are using a recent version of Node.
0 kommentar(er)
