📤
Publishing on deno.land/x
The easy way is to just git add the deno_dist directory to your project, heads over to deno.land/x and register your module specifying
deno_dist
as subdirectory
deno_registration
deno.land/x doesn't allow the
-
character, if your module contain some, use _
insted. Example:
foo-bar
-> foo_bar
deno_dist
is not source code. It shouldn't be tracked by git to avoid that we need a CI workflow that, when we release: - Create a
tmp_branch
- Builds locally, there by creating the
deno_dist/
directory. - Remove
/deno_dist
from the.gitignore
- Commit all
deno_dist/*
files (the commit exist only on thetmp_branch
). - Creates a new GitHub release targeting
tmp_branch
- Release on NPM
- We remove the
tmp_branch
If you want more infos about this workflow you can follow this PR where I set it up on the
ts-pattern
repo.Last modified 7mo ago