Search Results for "file::rsyncp"

... be relatively large. A zipped, minimal Electron application is approximately the same size as the zipped prebuilt binary for a given target platform, target arch, and Electron version (files named electron-v${version}-${platform}-${arch}.zip). Building an Electron app for the Windows target platform requires editing the Electron.exe file. Currently, Electron Packager uses node-rcedit to accomplish this.

Get the current package's binary path (using the package.json bin field). This is useful when testing a package's binary. Using get-bin-path (as opposed to hard-coding the path to the binary). Validates that the package.json bin field is correctly setup. Decouples the binary path from the tests, which allows moving the file without rewriting the tests. This package is an ES module and must be loaded using an import or import() statement, not require(). Returns the current package's binary...

Add it to your scripts in package.json. Or you can use it with npx from NPM 5.2+. bundlesize accepts an array of files to check. You can give a different file by using the --config flag. If the names of your build files are not predictable, you can use the glob pattern to specify files. This is common if you append a hash to the name or use a tool like create-react-app/nextjs. It will match multiple files if necessary and create a new row for each file. By default, bundlesize gzips your build...

npm-check-updates upgrades your package.json dependencies to the latest versions, ignoring specified versions. Maintains existing semantic versioning policies, i.e. "express": "^4.0.0" to "express": "^5.0.0". Only modifies package.json file. Run npm install to update your installed packages and package-lock.json. Show any new dependencies for the project in the current directory. Make sure your package file is in version control and all changes have been committed. This will overwrite your...

Download a specific version of Node.js. The Node.js release is downloaded, uncompressed and untared to an executable file ready to run. node >=14.18.0 must be globally installed. However any Node version can be downloaded. This package is an ES module and must be loaded using an import or import() statement, not require(). Node.js binary's CPU architecture. This is useful for example when you're on x64 but would like to run Node.js x32.

... requires npm. To use release-it, a package.json file is not required. The recommended way to install release-it also adds basic configuration. You will be prompted to select the new version, and more prompts will follow based on your setup. Run release-it from the root of the project to prevent potential issues. Out of the box, release-it has sane defaults, and plenty of options to configure it.

Vue CLI is the Standard Tooling for Vue.js Development. Vue CLI provides a great number of features including out-of-the-box support for TypeScript, Babel, PostCSS, ESLint, PWA, as well as Unit Testing and End-to-end Testing. It comes with its own graphical user interface and a plugin system that allows for the building and sharing of reusable solutions that can answer common needs. Vue CLI provides instant prototyping with a single Vue file, and is fully configurable with no need for ejecting...