Skip to content

Swtich to Deno from Node #3

@johncmanuel

Description

@johncmanuel

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

N/A

Describe the solution you'd like
A clear and concise description of what you want to happen.

Switch from using Node to Deno for managing frontend dependencies, builds, and tooling. This would eliminate the need to maintain several frontend developer tools such as Prettier, ESLint, etc. since Deno has their own equivalent.

Migrating to Deno would require reconfiguring the GitHub workflows and wails.json, and cleaning up files not needed anymore such as Prettier config, tsconfig, etc.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

There is also Bun, which is a decent alternative. It's very fast, which I personally like, but as far as I know, it lacks the tooling I've mentioned earlier.

Additional context
Add any other context or screenshots about the feature request here.

N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions