Nuxt•2mo ago

ohash error eferenceError: Cannot access 'defaults' before initialization

Nitro fails to starts: I've tracked the problem to ohash function:

function objectHash(object, options) {
  if (options) {
    options = { ...defaults, ...options };
  } else {
    options = defaults;
  }
  const hasher = createHasher(options);
  hasher.dispatch(object);
  return hasher.toString();
}

function objectHash(object, options) {
  if (options) {
    options = { ...defaults, ...options };
  } else {
    options = defaults;
  }
  const hasher = createHasher(options);
  hasher.dispatch(object);
  return hasher.toString();
}

How to solve this?

30 Replies

kapa.ai•2mo ago

Hi @Frox. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Based on the information provided in the knowledge sources, I don't have enough specific details to directly address the ohash error you're encountering. However, I can provide some context and a potential solution based on recent updates to the ohash package used by Nuxt. The error you're seeing suggests that there's an issue with accessing the defaults variable before it's initialized in the objectHash function. This could be related to a recent update in the ohash package. According to the ohash update pull request, Nuxt recently updated its dependency on ohash from version ^1.1.3 to ^1.1.4. This update included some fixes and improvements, particularly to the murmurHash implementation. To potentially resolve this issue, you could try the following steps: 1. Update your Nuxt project dependencies to ensure you're using the latest version of ohash. 2. If you're using npm, run:

   npm update ohash

   npm update ohash

If you're using yarn, run:

   yarn upgrade ohash

   yarn upgrade ohash

3. After updating, rebuild your Nuxt project. If the issue persists after updating, it might be worth checking your Nuxt configuration and any custom implementations that might be interfacing with ohash. If you continue to encounter this error, I recommend reporting it as an issue on the Nuxt GitHub repository, providing details about your Nuxt version, configuration, and a minimal reproduction of the error. Remember, always backup your project before making any significant changes or updates. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•2mo ago

<@252212996334551040> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

FroxOP•2mo ago

Ok the issue is the new update of h3 https://github.com/unjs/h3/releases Downgrading to 1.15.0 resolved it. But the thing is nitro uses h3 as dep: "h3": "^1.15.0",

GitHub

Releases · unjs/h3

⚡️ Minimal H(TTP) framework built for high performance and portability - unjs/h3

FroxOP•2mo ago

@danielroe FYI @pi0

pi0•2mo ago

@Frox what version of nitro are you using? please report it as an issue if you can with reproduction to nitro repo

FroxOP•2mo ago

Hi @pi0 Thank you for response: I use nuxt: 3.15.4 Which uses "nitropack": "^2.10.4", I have installed version:

"node_modules/nitropack": {
            "version": "2.10.4",

Before it was installing h3: 1.15.0 But Today I had to delete package-lock.json And h3: 1.15.1 was installed and causing this issue as a workaround i locked h3 to 1.15.0 becuase was affecting production

Danny Vogel•2mo ago

this randomly started happening to my production build as well, thanks so much for posting @Frox . Will try your workaround and report back using override with h3 1.15.0 worked, thanks again @Frox .

FroxOP•2mo ago

Happy it helped to you too, but why patch version of h3 breaks nitro 🥲

Danny Vogel•2mo ago

yeah...gonna see if I can create a reproduction to create an issue in the nuxt github repo

FroxOP•2mo ago

@Danny Vogel I think is somethig to do with useCookies

FroxOP•2mo ago

Also think is related to this as well: https://github.com/nitrojs/nitro/issues/3123

GitHub

The requested module 'ohash' does not provide an export named 'dige...

Environment nitro: npm:nitropack-nightly@latest node: 20 nuxt 3.15.4 Reproduction update dependencies in pnpm to latest version and try to run a nuxt application. Describe the bug The requested mod...

FroxOP•2mo ago

And is all related to this change: https://github.com/unjs/h3/compare/v1.15.0...v1.15.1

GitHub

Comparing v1.15.0...v1.15.1 · unjs/h3

⚡️ Minimal H(TTP) framework built for high performance and portability - Comparing v1.15.0...v1.15.1 · unjs/h3

Danny Vogel•5w ago

tried a minimal repo with one server route setting the cookie and another getting the cookie and the error isnt ocurring. Can't seem to reproduce it today im getting this randomly, I assume its a similar issue:

ReferenceError: Cannot access 'nativeFuncLength' before initialization.
      at isNativeFunction (/app/.output/server/chunks/nitro/nitro.mjs:6060:69)
      at function (/app/.output/server/chunks/nitro/nitro.mjs:5999:9)
      at array (/app/.output/server/chunks/nitro/nitro.mjs:5950:14)
      at object (/app/.output/server/chunks/nitro/nitro.mjs:5923:14)
      at serialize (/app/.output/server/chunks/nitro/nitro.mjs:5889:10)
      at hash (/app/.output/server/chunks/nitro/nitro.mjs:5885:53)
      at defineCachedEventHandler (/app/.output/server/chunks/nitro/nitro.mjs:6213:34)
      at /app/.output/server/chunks/nitro/nitro.mjs:5015:17

ReferenceError: Cannot access 'nativeFuncLength' before initialization.
      at isNativeFunction (/app/.output/server/chunks/nitro/nitro.mjs:6060:69)
      at function (/app/.output/server/chunks/nitro/nitro.mjs:5999:9)
      at array (/app/.output/server/chunks/nitro/nitro.mjs:5950:14)
      at object (/app/.output/server/chunks/nitro/nitro.mjs:5923:14)
      at serialize (/app/.output/server/chunks/nitro/nitro.mjs:5889:10)
      at hash (/app/.output/server/chunks/nitro/nitro.mjs:5885:53)
      at defineCachedEventHandler (/app/.output/server/chunks/nitro/nitro.mjs:6213:34)
      at /app/.output/server/chunks/nitro/nitro.mjs:5015:17

pi0•5w ago

Anyone experiencing similar issues related to ohash, meanwhile before nuxt minor release with ohash v2 migration, please make sure there is no node_modules/ohash in your project or if it is node_modules/ohash/package.json version is 1 (adding ohash@^1 as dependency might help but then you have to revert)

FroxOP•5w ago

Hi @pi0 After upgrading nitro as well, I get now a different error:

const hasher = new Hasher();
                 ^

ReferenceError: Cannot access 'Hasher' before initialization

const hasher = new Hasher();
                 ^

ReferenceError: Cannot access 'Hasher' before initialization

FroxOP•5w ago

Comes from: https://github.com/nitrojs/nitro/blob/67c396ba109ec209584a4603b72a2905308ad08c/src/runtime/internal/hash.ts

GitHub

nitro/src/runtime/internal/hash.ts at 67c396ba109ec209584a4603b72a2...

Next Generation Server Toolkit. Create web servers with everything you need and deploy them wherever you prefer. - nitrojs/nitro

Danny Vogel•5w ago

hi @Frox I had the same issue. I created an issue in the nuxt repo (maybe should have gone to nitro repo) https://github.com/nuxt/nuxt/issues/31222. Essentially I just ended up reverting to older versions to keep things working with this:

 "nuxt": "3.13.2",
  },
  "overrides": {
    "nitropack": "2.10.4",
    "h3": "1.15.0"
  }

 "nuxt": "3.13.2",
  },
  "overrides": {
    "nitropack": "2.10.4",
    "h3": "1.15.0"
  }

GitHub

Issues · nuxt/nuxt

The Intuitive Vue Framework. Contribute to nuxt/nuxt development by creating an account on GitHub.

FroxOP•5w ago

Yes worked, thnak you @Danny Vogel another few hours wasted 😄

Danny Vogel•5w ago

yeah spent most of my work day on this, very annoying

danielroe•5w ago

looking into this. can either of you provide a repro?

Danny Vogel•5w ago

missed this message though I responded in the github issue too. I was unable to reproduce it on stackblitz as im not sure what specific conditions are needed for it to trigger. maybe @Frox can share a bit about his implementation to see if we can find some commonalities. Saw you committed a fix, hope that does it! Thanks

FroxOP•4w ago

@danielroe after upgrading to nuxt 3.16.0 seeing `Error: Cannot access 'Hasher' before initialization | Nuxt @Danny Vogel do you have the same?

FroxOP•4w ago

Danny Vogel•4w ago

I haven't upgraded on my main work project! prefer staying on older versions for now

FroxOP•3w ago

@Danny Vogel Good news I've managed to create reproduction: https://stackblitz.com/edit/github-8y9ws25x Updated your issue on Github

Sergkei Melingk

StackBlitz

Nuxt - Starter - StackBlitz

Create a new Nuxt project, module, layer or start from a theme with our collection of starters.

Danny Vogel•3w ago

oh wow nice, yeah I got the error when I ran it too. hope that helps them fix it!

FroxOP•3w ago

@Danny Vogel you also use defineCachedFunction ?

Danny Vogel•3w ago

I don't actually haha. so it must not just be that I just use defineEventHandler and dont think I do anything too fancy mostly returning a simple JSON, setting/deleting cookies and also using sendRedirect oh and using some encrypting/decrypting methods using crypto and elliptic

danielroe•3w ago

have you created/updated a nitro issue with this repro?

FroxOP•3w ago

Thank to @pi0 he did it, https://github.com/nitrojs/nitro/issues/3225 I think we can then close this, and continue on github.

GitHub

Error: Cannot access 'Hasher' before initialization · Issue #3225 ·...

Environment [email protected] Reproduction import { defineNitroConfig } from 'nitropack/config' export default defineNitroConfig({ handlers: [ {route: "/", handler: "~/index.t...

Gaming

Programming

ohash error eferenceError: Cannot access 'defaults' before initialization

Did you find this page helpful?