Concept
Service discovery via package.json
Servix finds a service entry through the servix.entry field in package.json, so any compatible npm package is installable by name.
Problem
Without a discovery contract, installing a service would require knowing its internal file layout.
Mental model
package.json declares where the service definition lives; the CLI does the rest.
Declare the Servix entry in package.json:
{
"name": "@x12i/my-service",
"servix": {
"entry": "dist/servix.service.js"
}
}
Then servix install @x12i/my-service resolves the entry automatically. During development, servix install ./dist/servix.service.js bypasses discovery with a direct path.