S
Supabase•2mo ago
johnny⑤

npm package can't be found after update to supabase 2.39.x

The project has been running fine, and in fact if i downgrade locally i can get it to work fine with any previous version. supabase version 2.32.0 through 2.38.0 works (tested major releases (x.0) only) supabase version 2.39.0 is the first that shows this problem. likely closely related to supabase-edge-runtime-1.69.1. the error: 
Could not find a matching package for 'npm:@mastermindzh/composable-json-stringify' in the node_modules directory. Ensure you have all your JSR and npm dependencies listed in your deno.json or package.json, then run `deno install`. Alternatively, turn on auto-install by specifying `"nodeModulesDir": "auto"` in your deno.json file.
        at file:///opt/atlassian/pipelines/agent/build/supabase/functions/deps.ts:47:8
Could not find a matching package for 'npm:@mastermindzh/composable-json-stringify' in the node_modules directory. Ensure you have all your JSR and npm dependencies listed in your deno.json or package.json, then run `deno install`. Alternatively, turn on auto-install by specifying `"nodeModulesDir": "auto"` in your deno.json file.
        at file:///opt/atlassian/pipelines/agent/build/supabase/functions/deps.ts:47:8
abbreviated deps.ts, showing the package fro mthe error 
// a composable JSON.stringify replacement
export {
  stringify,
  bigIntToString,
  dateToISOString,
  symbolToString,
  errorToObject,
  mapToObject,
  setToArray,
} from "npm:@mastermindzh/composable-json-stringify";
export type { JsValue } from "npm:@mastermindzh/composable-json-stringify";
// a composable JSON.stringify replacement
export {
  stringify,
  bigIntToString,
  dateToISOString,
  symbolToString,
  errorToObject,
  mapToObject,
  setToArray,
} from "npm:@mastermindzh/composable-json-stringify";
export type { JsValue } from "npm:@mastermindzh/composable-json-stringify";
Essentially, something must have changed in the latest minor version of supabase and the used edge runtime that causes this problem, in otherwise correct code. In fact, after some miscommunication this version of the sources is actually deployed to the cloud and it's running just fine. in practice this occurs when running locally and during deployment pipelines. locally, it was easy to verify, this npm package IS PRESENT on the filesystem in the project, it resolved and downloaded correctly! what changes are causing this? and what change is expected to be made in the sources to resolve this? ```
6 Replies
johnny⑤
johnny⑤OP•2mo ago
small update, my colleague has pinpointed including bugfix versions. 2.38.1 is het first one that reveals this problem.
garyaustin
garyaustin•2mo ago
If you think you have found an issue in edge functions make sure to check the repository and the releases beyond the one you mention. https://github.com/supabase/edge-runtime So far no user seems to hit this, or have ideas for you.
johnny⑤
johnny⑤OP•2mo ago
this issue seems the same, while the error differs, the theory of npm packages not being available in the docker feels like mine. https://github.com/supabase/edge-runtime/issues/410 unfortunately, that issue was supposedly fixed. But of course it might be reintroduced. We also observe that this only occurs on windows machines. a linux user in the company does not experience this issue with the version i reported.
GitHub
InvalidWorkerCreation: worker boot error: failed to create the grap...
Bug report I confirm this is a bug with Supabase, not with my own application. I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug When I serve a function locally ...
garyaustin
garyaustin•2mo ago
Probably best to open issue in the repository. Unless other users come along your findings won’t be seen by Supabase here.
johnny⑤
johnny⑤OP•2mo ago
thanks, will do that first thing in the morning then
johnny⑤
johnny⑤OP•2mo ago
the ticket can be found here: https://github.com/supabase/supabase/issues/38402
GitHub
npm package can't be found after update to supabase 2.39.x · Issue...
Bug report Before posting here: I queried on discord and was advised to post here I confirm this is a bug with Supabase, not with my own application. I confirm I have searched the Docs, GitHub Disc...

Did you find this page helpful?