$ deno --version
deno 2.3.5 (stable, release, x86_64-pc-windows-msvc)
v8 13.7.152.6-rusty
typescript 5.8.3

I have a project with the following import map:

"imports": {
    "@minecraft/server": "npm:@minecraft/[email protected]"
}

Some members of my team and I were previously on deno 2.2.x and our imports were fine.

import { world } from "@minecraft/server";

Now, on 2.3.5, we are all getting this warning:

NPM package "@minecraft/[email protected]" does not define an export ".".

The type definitions still work in the deno LSP, and we have no issues with compilation. However, the warning is new and the old behavior from 2.2.x is what is expected in this case.

I've tried using explicit npm: specifiers, but that does not resolve the warning either. Checking if the types are correct reveals that they seem to be.