Graeme Comments - Answer Overflow

Graeme

•Created by Graeme on 7/11/2023 in #help

ERR_PACKAGE_PATH_NOT_EXPORTED on 0.27.1

I have found the issue and can confirm it's our side. A process we previously relied on was removed and local packages were not installed. oopsie 🙈. Happy to leave this here for anyone who falls into a similar hole. Equally happy for it to be removed if no longer relevant. ✌🏻

4 replies

DTDrizzle Team

•Created by Graeme on 7/11/2023 in #help

ERR_PACKAGE_PATH_NOT_EXPORTED on 0.27.1

I manually added the following to node-modules/drizzle-orm/package.json so I can continue but can only be temporary of course.

"./expressions": {
  "types": "./index.d.ts",
  "import": "./index.mjs",
  "require": "./index.cjs",
  "default": "./index.mjs"
},
"./sql": {
  "types": "./index.d.ts",
  "import": "./index.mjs",
  "require": "./index.cjs",
  "default": "./index.mjs"
},

"./expressions": {
  "types": "./index.d.ts",
  "import": "./index.mjs",
  "require": "./index.cjs",
  "default": "./index.mjs"
},
"./sql": {
  "types": "./index.d.ts",
  "import": "./index.mjs",
  "require": "./index.cjs",
  "default": "./index.mjs"
},

Perhaps this helps?

4 replies

DTDrizzle Team

•Created by Graeme on 6/27/2023 in #help

Unexpected type mismatch for sqlite integer boolean mode

Thanks @Andrew Sherman

9 replies

DTDrizzle Team

•Created by Graeme on 6/27/2023 in #help

Unexpected type mismatch for sqlite integer boolean mode

Only one way to find out... but just keen to discuss it so I ensure I'm not misinterpreting 🙂

9 replies

DTDrizzle Team

•Created by Graeme on 6/27/2023 in #help

Unexpected type mismatch for sqlite integer boolean mode

Yeah, it makes sense logically for sure. I think the confusion lies wherein the type is an integer with a boolean "mode". Drizzle also state it's set as a 0 or 1.

This allows you to operate boolean values in your code and Drizzle stores them as 0 and 1 integer values in the database.

Is there a transformation under the hood going on or am I reading too much into this? My understanding was that we should be doing this

mutation({
  isFooBar: 0 // 0 is entered into the db
})

mutation({
  isFooBar: 0 // 0 is entered into the db
})

But are we saying we should be doing:

mutation({
  isFooBar: false // 0 is still entered into the db
})

mutation({
  isFooBar: false // 0 is still entered into the db
})

9 replies

Gaming

Programming