[3.1.2] Deprecation: How to use getUrlForPackage()?

[richb-hanover]

A small project was working fine with Snowpack 3.0.11. I upgraded with yarn add snowpack and the package.json file now lists "snowpack": "^3.1.2",

yarn start seems to progress until it hits the message below. (I suspect it's complaining about a line import dayjs from "dayjs";

How can I fix/workaround this? Many thanks!

[22:38:59] [snowpack] (/_snowpack/pkg/dayjs) Deprecated manual package import. Please use snowpack.getUrlForPackage() to create package URLs instead.

Update: the console shows this message:

Loading failed for the module with source “http://localhost:8080/_snowpack/pkg/dayjs”.

and the browser debugger shows line 1 of the file as import dayjs from "../_snowpack/pkg/dayjs";, and that file does not exist in _snowpack/pkg (In fact, there's no pkg directory inside _snowpack) Here's the full output...

 % yarn start
yarn run v1.22.10
warning ../package.json: No license field
$ snowpack dev
[18:36:14] [snowpack] Server started in 22ms.
[18:36:14] [snowpack] Local: http://localhost:8080
[18:36:14] [snowpack] Network: http://192.168.253.116:8080
[18:36:15] [@snowpack/plugin-typescript] 5:35:15 PM - Starting compilation in watch mode...
[18:36:15] [snowpack] (/_snowpack/pkg/dayjs) Deprecated manual package import. Please use snowpack.getUrlForPackage() to create package URLs instead.
[18:36:16] [@snowpack/plugin-typescript] 5:35:16 PM - Found 0 errors. Watching for file changes.
⠦ watching for file changes...

[arda-]

I'm having a similar issue; running pnpm start (which runs snowpack dev under the hood) causes it to fail to find the imports, but typing snowpack dev manually allows it to run fine.

[richb-hanover]

Update: I have worked around the problem (possibly it's a real solution...)

It turns out that my snowpack.config.js file sets packageOptions.source="remote", which causes the error message. Commenting out that line makes it go away. Here's a repo that reproduces the problem: https://github.com/richb-hanover/snowpack-getUrlForPackage

I looked through my commit history to see where this line came from: I started the project with Snowpack 2.0.something. When I converted to a 3.0.x version, I appear to have added the packageOptions.source="remote" line.

Commenting it out causes the error to go away for Snowpack 3.1.2...