support for deno

[ivanhofer]

deno is an alternative to Node.js. It has TypeScript support out-of-the-box. It would be nice to be able to use typesafe-i18n with deno.

• investigate what is needed to add support for deno
  • all imports need to include the file-ending *.ts:
    • update file generation to include file endings when outputting for deno (adapter: 'deno')
  • how can we import (only) types in deno??
    • find a solution to that problem
• re-write watcher to be able to run with deno instead of node

[zabihexes]

btw it works with deno now through deno npm specifiers.

[ivanhofer]

Thanks for checking!

[aW4KeNiNG]

Yes, I can confirm that it works on Deno. But the problem is that the Deno resolver can't find the module because the extension is missing in the imports. It compiles, but the intellisense is missing with this error:

Deno: Unable to load a local module: "./src/i18n/i18n-util". Please check the file path.

If I add the .ts extension in all imports it works fine and I can see intellisense for VSCode or IntelliJ.

For example, the i18n-util.sync.tsfile:

import { initFormatters } from './formatters.ts';
import type { Locales, Translations } from './i18n-types.ts';
import { loadedFormatters, loadedLocales, locales } from './i18n-util';

import de from './de/index.ts';
import en from './en/index.ts';
import it from './it/index.ts';

But, ofc, I can't overwrite them because these files are autogenerated.

[aW4KeNiNG]

Thanks!! It works :)

The only issue I'm encountering is that changing a string or adding a new one in the location file does not regenerate the files as it does in Node. It only works the first time the command is executed. Do you have any idea what might be causing this problem?

Note: you can update deno using deno upgrade.

[ivanhofer]

The only issue I'm encountering is that changing a string or adding a new one in the location file does not regenerate the files as it does in Node. It only works the first time the command is executed. Do you have any idea what might be causing this problem?

The generator uses chokidar. Maybe it does not detect changes when running in a deno process. You will probably need to prefix your command with a watcher package that is compatible with deno and disable the built-in watcher via --no-watch.

As I'm not aware of the deno ecosystem, I have left out some implementation details. It would be vreat if anyone could fill out any of the missing pieces:

• get a list of all installed dependencies (see TODOs here) see the node implementation as a reference
• add support for deno.jsonc (see here)
• write docs similar to those for the node-adapter here
• create a small example repository

[aW4KeNiNG]

Ok, thanks. It is weird, because sometimes it seems to work until I kill the process. I will check if I see something else or find the issue.

[zabihexes]

The only issue I'm encountering is that changing a string or adding a new one in the location file does not regenerate the files as it does in Node. It only works the first time the command is executed. Do you have any idea what might be causing this problem?

The generator uses chokidar. Maybe it does not detect changes when running in a deno process. You will probably need to prefix your command with a watcher package that is compatible with deno and disable the built-in watcher via --no-watch.

As I'm not aware of the deno ecosystem, I have left out some implementation details. It would be vreat if anyone could fill out any of the missing pieces:

* get a list of all installed dependencies (see `TODO`s [here](https://github.com/ivanhofer/typesafe-i18n/blob/main/packages/cli/src/setup/runtimes/deno.mts)) see the `node` implementation as a reference

* add support for `deno.jsonc` (see [here](https://github.com/ivanhofer/typesafe-i18n/blob/main/packages/cli/src/setup/runtimes/deno.mts#L13))

* write docs similar to those for the `node`-adapter [here](https://github.com/ivanhofer/typesafe-i18n/blob/main/packages/adapter-node/README.md)

* create a small example repository

I do not think detection Deno by looking for deno.json is a good idea. It can be .json or .jsonc btw. Also it is not required. You can use deno without it. You can even name the deno file differently....
I would suggest doing something like this instead.
https://github.com/aaronccasanova/aacc/blob/main/packages/cross-runtime/src/utils.js#L33

[ivanhofer]

I would suggest doing something like this instead.
aaronccasanova/aacc@main/packages/cross-runtime/src/utils.js#L33

Perfect, thanks for the hint! That is exactly what I was looking for.