GoogleChromeLabs/comlink

Find a way to support Deno and TS with the same code base

Open

#553 opened on Jul 13, 2021

View on GitHub
 (2 comments) (5 reactions) (0 assignees)TypeScript (10,359 stars) (382 forks)batch import
help wanted

Description

Currently, you can use Comlink in Deno through one of the npm CDNs (unpkg, skypack etc). But it’d be nice to be able to import the source from GitHub directly. This currently doesn’t work as TypeScript enforces either no file extensions in imports or .js extension, while Deno requires the actual file path (ending in .ts).

Contributor guide

Tech stack
typescriptdeno
Domain
developer experiencetooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
TypeScript module resolutionDeno module system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate how to make TypeScript imports compatible with both Deno and Node.js environments. Deno requires .ts file extensions while TypeScript typically uses .js or no extension. Consider using a build step that conditionally emits different imports, or explore Deno's support for npm packages and conditional exports. Look at similar projects that support both runtimes, such as those using esbuild or dual package patterns. Check existing comments in the issue for any suggested approaches.