-
Notifications
You must be signed in to change notification settings - Fork 72
add support for deno #472
Copy link
Copy link
Open
Labels
problem: removed issue templateOP removed the issue template without good causeOP removed the issue template without good causescope: integrationRelated to an integration, not necessarily to core (but could influence core)Related to an integration, not necessarily to core (but could influence core)
Description
Metadata
Metadata
Assignees
Labels
problem: removed issue templateOP removed the issue template without good causeOP removed the issue template without good causescope: integrationRelated to an integration, not necessarily to core (but could influence core)Related to an integration, not necessarily to core (but could influence core)
Troubleshooting
What happens and why is it incorrect
recently I've been trying to move my entire design-system build and test process to Deno.
what makes it hard is the different approach between nodejs typescript and deno typescript module path-finding methods.
deno wants us to import modules by file name extension like "../foo/bar.ts" but the node says we must import
tsandjswithout the file extension. currently, I solve this by creating different workspaces for my front-end and builder codes that use Deno.is there any way we can configure the bundler to ignore file extension so it would be acceptable by both rollup-typescript2 and Deno?
Environment
Deno and windows
the repository I'm working on is https://github.com/javadbat/design-system
Versions
1.4