Publishing (and configuring) the webhook for deno.land from monorepo

Thanks in advance for your help! I went through the setup on https://deno.com/add_module for my jupyter project anywidget (https://github.com/manzt/anywidget/pull/311) to support module for deno jupyter. Anywidget is a monorepo of a Python package and associated front-end JavaScript modules. I have github actions setup to make a separate tagged release for each sub-package, and would like to similarly support the deno module I created for interfacing with these front-end modules. - Is it possible to configure a different sub-path within the repo? (I'm not sure I did this correct, or may want to move mod.ts) - I'm not sure how the deno mod.ts will get published for other tagged releases of different packages. Is is possible to publish this separately? I'd ideally like to keep these all in the same repo, but understand if that is not possible. In that case, is it possible to transfer anywidget from deno.land (which I grabbed) to a separate repo?
Third Party Modules | Deno
Register a module with the third party registry.
accept imports in deno anywidget by rgbkrk · Pull Request #311 · ma...
This is a rough way to include imports, which could be a general preamble instead. import { widget } from "./mod.ts"; let model = await widget({ // shared model between frontend and ...
DAHDeno AI Helper10/2/2023
Based on the documentation, Deno is not prescriptive about how developers make their modules available—modules may be imported from any source. However, to publish Deno modules via the official deno.land/x hosting service, modules must be developed and hosted in public repositories on GitHub. Their source is then published to deno.land/x on tag creation. To answer your questions: 1. Configuring a different sub-path within the repo: The documentation does not provide explicit information on configuring a different sub-path within the repo for the Deno module. However, the module can be accessed by using a URL in the following format: https://deno.land/x/<module_name>@<tag_name>/<file_path>. This suggests that you can specify a sub-path in the <file_path> part of the URL. 2. Publishing the mod.ts for other tagged releases: The documentation states that module versions are persistent and immutable. It is thus not possible to edit or delete a module (or version), to prevent breaking programs that rely on this module. However, it does not provide explicit information on publishing the mod.ts separately for other tagged releases of different packages. 3. Keeping all in the same repo: The documentation does not provide explicit information on whether it's possible to keep all modules in the same repo. However, it does state that modules must be developed and hosted in public repositories on GitHub, suggesting that each module should have its own repository. 4. Transferring anywidget from deno.land to a separate repo: The documentation does not provide explicit information on transferring a module from deno.land to a separate repo. However, it does state that modules may be removed if there is a legal reason to do so (for example copyright
DAHDeno AI Helper10/2/2023
infringement). Please note that the information provided here is based on the documentation's opinion and may not cover all possible scenarios or use cases. For more specific or complex questions, it might be best to reach out to the Deno community or maintainers directly.
This isn't exactly what I needed.
Silly bot. @bartlomieju who's the right person to reach out to about figuring out deno.land registry issues? Just noticed this comment: https://discord.com/channels/684898665143206084/1158338786393079849/1158414995923677375
Email modules@deno.com
Sorry, was out for a few hours. Yeah the email above is go to solution 🙂
Thank you so much!!! If anyone finds this in the future, you can use the subdir and version_prefix search params for the webhook to configure where the root directory for your deno module lives and what tags trigger releases.

Looking for more? Join the community!

Recommended Posts
Looking for a Dev who is well-versed in Fast-Delivery of building front-end pages using React.js forLooking for a Dev who is well-versed in Fast-Delivery of building front-end pages using React.js forHow to assert object with a field of a given type?Hi, I'm writing an integration test that needs to assert an object response, where the ID field can Deno + LitHey how can use the [Lit](https://lit.dev/) framework with Deno? Is there a guide or config on how tIssues with Crypto Subtle Digest ext:deno_crypto/00_crypto.jsCurrently we are using `deno_core v0.200.0` `deno_runtime v0.123.0` when attempting to invoke `cryptAnyway to use deno fmt within a script itself without having to call deno again?I am working on a code generator and I'd like to run a string through deno fmt before I save to fileinteraction_endpoint_url: couldn't be verifiedI'm trying to create an http interactions bot using deno deploy, but sometimes my url fails to be veLost access to deno land module, how to reset the repo?My repository was accidentally destroyed on GitHub and I recreated it the same exact way. The webhooBDD with async testsI'd like to run some tests that all call the same helper function that wraps the bdd `it` function. Is there a schedule / pattern for which Deno releases get new Docker files?We'd love to update to Deno 1.37.1 in production, but deno_docker is still at 1.37.0. I've noticed tIs the Fresh compornents test function enabled?Attempting to write a test for Fresh compornents. I was able to verify the rendered content. I am Inquiry Regarding Deno Security Model and Command Injection VulnerabilityI am currently instructing a class on software security and have been exploring Deno's security mode`WARNING: v8::OwnedIsolate for snapshot was leaked` and/or crash after using snapshotOn startup, I create a runtime: ```rust let js_runtime = JsRuntimeForSnapshot::new(deno_corOak: Remove HTML extensions when serving filesUsing Oak, how can I serve `home.html` as `/home` (or `/home/`). I'm aware that `Context#send` existdeno_console not being properly instantiated?Not sure if it's indended, or if I am missing a step, but several core extensions, for example the dTailwind nonfunctional on fresh-update from 1.3.1 -> 1.4.3After running `deno run -A -r https://fresh.deno.dev/update .` on my project, the tailwind styles doassertEquals deprecated in vscode?Since upgrading to std@0.202.0 I'm seeing that assertEquals is marked deprecated, but I can't see whForce await import() to import a fresh copy?I have a Deno instance that dynamically loads a module with: `await import("some/module.js")` The mFresh ClassList Brokenhttps://github.com/Leave TLS connection open in between testsWhen I have 2 tests that use a database connection and attempt to close the connection `afterAll` thNvim tsserver clash with denolsI have read the docs and added a root_dir in my lua lsp file but for some reason tsserver still lanc