Jake Bailey
Jake Bailey
This packs doesn't exist or is private: https://www.npmjs.com/package/@adobe/ccweb-add-on-sdk
Yes, I noticed that after commenting. I'm still not sure that this is a good setup; we have no prior art of any package declaring a URL as its module...
Can you give an example of code that produced that error? I would think you can write: ```ts import { Something } from "./otherFile"; declare module "https://some.url/foo/bar" { export {...
I looked at your repro, and this code works: ``` import File1Types from "./file1"; declare module "myModule1" { export default File1Types; export * from "./file1"; } import File2Types from "./file2";...
I see what you mean; I think I'll have to ask around to see if anyone has any opinions. Declaring a URL is not something anyone has done on DT...
Been chatting with people, and one thing I thought of was that you could generate a `d.ts` file in the user projects... and then I discovered that you're already doing...
Okay; if we're going to have a wrapper package on DT, then I think it would be better to not have it partially declared here and partially in your package;...
Is there any chance you could commit that example to a repo? I'd be happy to take a look.
Okay, I can reproduce that. I feel like it's a bug, but I guess for now I'll just okay this.
Once CI is passing, I can approve. You just need to remove the tslint config.