You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking to add bundled type definitions to the Pika CDN, so that any npm package that comes with types would have a single bundled .d.ts file available to complement it. From reading the deno manual, I understand that it will then be possible to do this:
// @deno-types="https://cdn.pika.dev/lodash-es/latest?types"
import * as foo from "https://cdn.pika.dev/lodash-es/latest";
Pika CDN bundles each package that it serves into a single ESM JS file that can be imported by Deno & Browsers. Since I have control over that file at build time, is there anything special I can do/add to have the https://cdn.pika.dev/lodash-es/latest file itself tell deno where it's type definition lives? That way, you could get rid of the user-provided // @deno-types= comment when using Pika CDN.
The text was updated successfully, but these errors were encountered:
Hey all,
I'm looking to add bundled type definitions to the Pika CDN, so that any npm package that comes with types would have a single bundled .d.ts file available to complement it. From reading the deno manual, I understand that it will then be possible to do this:
Pika CDN bundles each package that it serves into a single ESM JS file that can be imported by Deno & Browsers. Since I have control over that file at build time, is there anything special I can do/add to have the
https://cdn.pika.dev/lodash-es/latest
file itself tell deno where it's type definition lives? That way, you could get rid of the user-provided// @deno-types=
comment when using Pika CDN.The text was updated successfully, but these errors were encountered: