corestack_ node_ package_ lookup
Look up an npm package.
When to use it
Before adding a global package: whether it exists on the public npm registry, the exact version a selector resolves to, its description and licence, whether it has an install script, whether it is deprecated and its latest version. exists: null means the registry could not be asked; say so and let the person decide. No row is needed.
Ask for it
Using the Corefinity MCP server, call corestack_node_package_lookup with name sharp, selector 0.34. (Look up an npm package.) Tell me what it returned.Inputs
namestringRequired
The npm package name, e.g. sass or @angular/cli. Up to 214 characters.
selectorstring
A version, range or dist-tag (default latest). Up to 255 characters.
Example call
{
"name": "corestack_node_package_lookup",
"arguments": {
"name": "sharp",
"selector": "0.34"
}
}If it is refused
| Reason | What to do |
|---|---|
package_spec_invalid | A URL, git, file, alias or user/repo spec; only public registry packages can be installed. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |
The same task elsewhere
Was this helpful?