If you're running into issues with Component, the first step you should do is run
component validate. This will validate your
component.json files and tell you if there are any major issues with your
The next step is to use the
DEBUG environmental variable. Read more about how DEBUG works. For a quick debug statement, run your command prefixed with
DEBUG=component*. For example, this debugs a
component update command:
$ DEBUG=component* component update component-resolver remote not set - defaulting to ["github"] +0ms component-resolver:locals resolving local at "/Users/jong/Workspace/test" +0ms component-resolver resolving "asdf" +11ms component-resolver:locals resolving "asdf"'s local dependency "test". +5ms component-resolver:locals looking up "asdf"'s local dependency "test" at "/Users/jong/Workspace/test/lib/test". +0ms component-resolver remaining dependencies: 0 +1ms component-resolver remaining semver: 0 +0ms component-resolver:locals resolving local at "/Users/jong/Workspace/test/lib/test" +1ms component-resolver resolving "test" +2ms component-resolver remaining dependencies: 0 +0ms component-resolver remaining semver: 0 +0ms component-resolver:locals resolved local "asdf" +1ms component-resolver finished resolving locals +1ms component-resolver finished resolving dependencies (1) +0ms component-resolver finished installing dependencies +0ms update : updating asdf's pinned dependencies update : updated asdf's ranged dependencies in 743ms
You may also be interested in
DEBUG=remotes* for when dependencies don't install, specifically those
error : Error: no remote found for dependency "firstname.lastname@example.org". messages. Some common causes for this error are:
- The repository does not exist.
- The repository was deleted or has moved to a different location.
- The version specified does not have a
masterdoes. In this case, specify
masteras the version ask the maintainer to create a new release with a
Here's an example on debugging:
$ DEBUG=remotes* component install email@example.com remotes:local checking local components at /Users/jong/Workspace/test/components +0ms remotes:local resolving local remote +11ms remotes:local checking folder: /Users/jong/Workspace/test/components/es-shims/es5-shim +1ms remotes:github GET "https://raw.githubusercontent.com/es-shims/es5-shim/v2.3.0/component.json" +0ms remotes:github GET "https://raw.github.com/es-shims/es5-shim/v2.3.0/component.json" +352ms remotes:github GET "https://raw.githubusercontent.com/es-shims/es5-shim/v2.3.0/component.json" +284ms remotes:github GET "https://raw.github.com/es-shims/es5-shim/v2.3.0/component.json" +124ms error : Error: no remote found for dependency "firstname.lastname@example.org".
This shows you which URLs were tried, and since no remote was found, all of these URLs 404'd.