Importing and Requiring without explicit .civet extension

[thinkingofmaud]

To me, importing modules without using the .civet extension feels like the most natural way to using imports (or requires)

Unplugin integrations let you do that.

Civet/source/unplugin/unplugin.civet

Line 55 in 0d97621

civetExtension := /\.civet$/

---

Running with npx civet, though, I can only import by writing the full extension.

Coffeescript had built in support for the extension using require.

You just inject it onto the entry script and could require coffeescript as it was js.

https://github.com/jashkenas/coffeescript/blob/817c39a13065a900725943c33a79252a69d779e2/src/register.coffee#L32

'@danielx/civet/register' does not work like that

---

Using bun native support for typescript, and the plugin I could get imports working for compilerOptions specified paths. But not for relative paths. I could not get it working on node.

Here it is, if it helps any user:

//tsconfig.json
{
  "compilerOptions": {
    "paths": {
      "@/*": ["./*"]
    }
  },
  "include": ["**/*.civet"],
  "exclude": ["node_modules"]
}

You may also configure it to work only in specified paths by putting it on the path instead.