Question 1

How do I install a package with Trex in Deno?

Accepted Answer

Use trex install --map for deno.land packages, e.g., trex i --map fs http fmt, or --nest for nest.land with versions, like trex i --nest opine@0.13.0. Custom URLs can be added with --custom flag.

Question 2

Trex vs deno install: which should I use?

Accepted Answer

Trex adds convenience by automating import maps and supporting multiple registries, ideal for streamlined workflows. However, if you prefer Deno's native tools and don't need extra features, deno install might be simpler for basic tasks.

Question 3

Can Trex use packages from npm or other runtimes?

Accepted Answer

Trex is designed for Deno and primarily supports Deno-compatible registries. It can install from custom URLs, such as jspm.io for React, but doesn't natively handle npm packages without manual URL configuration.

Question 4

How do I update dependencies with Trex?

Accepted Answer

Use trex check to see outdated packages, but note it's limited to deno.land sources. Then update manually by reinstalling with new versions, or use trex upgrade for Trex itself. Future versions may expand support.

Question 5

Is Trex exec secure with default permissions?

Accepted Answer

By default, trex exec grants all permissions (--allow-all), which can be a security risk. You can specify permissions with --perms flag, e.g., trex exec --perms read,write denon, to limit access.

Question 6

How to create custom scripts with Trex run.json?

Accepted Answer

Create a run.json file with a scripts object defining aliases, like 'dev': 'denon run ./app.ts'. You can add lifecycle hooks and use the --watch flag for file watching, though with limitations for long-running processes.

trex

What is trex?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions