E0177 Behaviour file named or imported wrongly
Words in italics are filled in when the compiler reports it, such as the element's name or the list of known ones.
Why
The name decides what a behaviour file is: <name>.behaviour.duo or <name>.behaviour.ts, in any folder but pages/, where every file is a route (decision 0152). So the build refuses a behaviour file in pages/; one named .behavior anywhere in the project (the build, the checker and the editor would never know it); the same behaviour written twice, as name.behaviour.duo and name.behaviour.ts side by side; an import of one that is not there; a default or namespace import, which names nothing a behaviour file exports and cannot place it as a component; an import that names nothing, import "..." or import {} from "...", which would only run the file; and a .behaviour.ts file imported, or re-exported (export { a } from, export * from), by any .ts, .mts or .cts file of the project the build does not compile as a behaviour, such as a Node script, where it would run without the state rules.
How to fix it
Name the file <name>.behaviour.duo or <name>.behaviour.ts, keep one of the two, put it in behaviours/, and import its behaviours by name: import { calendar } from "../behaviours/calendar.behaviour.duo". Import only types from a .ts file that is not a page, component or behaviour.
In a terminal
duolith explain E0177