can start script have higher precedence than main?

[jfirebaugh]

A common scenario for me is to have a module with both a "main" file and a "start" script. The main file is for consumption by external modules and doesn't listen on a port at all. The start script does listen, and typically runs a server for in-browser tests, manual debugging, or examples. The current behavior of "main" having precedence over "start" doesn't work in this scenario, so I'm wondering if it can be reversed, or if there are scenarios where the current precedence makes more sense.

[typicode]

In next version, it won't be that opinionated. Though you can force start by adding a custom command when linking like this:

$ katon link 'npm start'

[typicode]

Hey, just released v0.5.0 which introduces many changes.
There's no more default behavior, which should make things more predictable.

You can migrate existing servers by using katon migrate.