For example, the bundle-text: scheme can be used to inline a compiled bundle as text. These allow you to specify a different pipeline to compile a file with than the default one. URL schemes #ĭependency specifiers may use URL schemes to target Named pipelines. Note: Query parameters are not supported for CommonJS specifiers (created by the require function). Tilde specifiers are useful for similar purposes as absolute specifiers, but are more useful when you have more than one package. A package root is a directory with a package.json file, which would typically be found in node_modules, or as the root of a package in a monorepo. Tilde specifiers start with ~, and resolve relative to the nearest package root from the importing file. The above example could be placed in any file, at any point in your project’s directory structure, and will always resolve to /path/to/project/src/client.js. Absolute specifiers could be useful to avoid very long relative paths in deeply nested hierarchies. yarn.lock or package-lock.json), or a source control directory (e.g.git). The project root is the base directory of your project, which would typically contain a package manager lock file (e.g.
Absolute specifiers #Ībsolute specifiers start with /, and resolve a file relative to the project root. When building for an Electron environment, the electron module is also considered a builtin and excluded from the bundle.
#PARCEL MINIFY FULL#
See the Node docs for a full list of builtin modules. When building for a node environment, builtin modules are excluded from the bundle, otherwise a shim is included. When a dependency specifier references one of these module names, the builtin module is preferred over any module installed in node_modules with the same name.
Parcel includes shims for many builtin Node.js modules, e.g. This could be a node_modules/lodash/clone.js file, for example. The above example resolves lodash within a node_modules directory as described above, and then resolves the clone module within the package rather than its main entrypoint. For example, a package may publish multiple entry points rather than only a single one. Package sub-paths #īare specifiers may also specify a sub-path within a package. See Package entries for more details on this process. Once a module directory is found, the package entry is resolved.
Node_modules directories are searched upwards from the importing file. The exact location will depend on the location of the node_modules directory, as well as configuration within the package. In the above example, react may resolve to something like /path/to/project/node_modules/react/index.js. path/to/project/src/client/index.js: import 'react' , and resolve a file relative to the importing file. In addition to the standard dependency specifiers supported across many tools, Parcel also supports some additional specifier types and features. It is responsible for turning a dependency specifier into an absolute path that can be loaded from the file system. Parcel implements an enhanced version of the Node module resolution algorithm. Typically, these dependencies do not specify a full absolute path, but rather a shorter specifier that is resolved to an absolute path by Parcel and other tools. For example, in JavaScript the import statement or require function may be used to create dependencies. Dependency specifiers #Ī dependency specifier is a string that describes the location of a dependency relative to the file that imports it.
#PARCEL MINIFY HOW TO#
Dependencies describe where to find the file containing the code you rely on, as well as metadata about how to build it. As Parcel builds your source code, it discovers dependencies, which allow code to be broken into separate files and reused in multiple places.
0 kommentar(er)
