Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`import { navigate }` internal assertion failed

See original GitHub issue

(congrats on the 0.1.0 release!)

Happy to put together a sandbox/repro, just let me know.

Code like this is failing for me, not within vite itself, but within my test suite (jest):

import { navigate } from 'vite-plugin-ssr/client/router';

    [vite-plugin-ssr@0.1.0][Internal Failure] You stumbled upon a bug in `vite-plugin-ssr`'s source code (an internal assertion failed). This should definitely not be happening, and you should create a new issue at https://github.com/brillout/vite-plugin-ssr/issues/new that includes this error stack (the error stack is enough to debug this). Or reach out on Discord. A fix will be written promptly.

      at Object.<anonymous> (node_modules/vite-plugin-ssr/client/router/index.node.ts:5:1)
      at Object.<anonymous> (node_modules/vite-plugin-ssr/client/router/index.js:2:18)
      at Object.<anonymous> (pages/session.page.tsx:29:1)
      at Object.<anonymous> (pages/__tests__/session.page.spec.tsx:2:1)

It seems like vite-plugin-ssr/client/router could either resolve to index.js or index.ts, and certain environments will prefer the index.js, which trips this internal assertion.

Issue Analytics

State:
Created 2 years ago
Comments:13 (13 by maintainers)

Top GitHub Comments

2reactions

brilloutcommented, Jun 11, 2021

The lead seems quite pushy about supporting Vite https://github.com/storybookjs/storybook/issues/14024. Probably only a question of time.

As for Deno, it’s more a Deno problem if you ask me. Deno is just too much of a drastic change for the ecosystem willing to migrate. The only real benefit of Deno is the ability the run scripts with lesser permissions, which so far hasn’t been a USP enough to justify migration cost. Hopefully things will change, I like Deno.

Let me know if you have further integration problems.

0reactions

brilloutcommented, Jun 11, 2021

(I care a lot about smooth integrations.)

Top Results From Across the Web

[v9.0.2 auth] INTERNAL ASSERTION FAILED: Expected a ...

I am currently using the following workaround. import { browserLocalPersistence, inMemoryPersistence, indexedDBLocalPersistence, initializeAuth ...

firebase - getting the following error when using firestore ...

getting the following error when using firestore Firestore: Error: FIRESTORE (8.1.2) INTERNAL ASSERTION FAILED: Unexpected state · Ask Question.

Internal Error in Geometry Decomposition - Knowledge Base

Solution. This error means that COMSOL Multiphysics failed to resolve the geometry relations. If your geometry consists of several objects, the objects are ......

Assertion failed: mi is not available, make sure it is properly ...

When I navigate to "Manage Role Based Permission Access", select "Add User" option, the following error message appears: "Assertion failed: mi is not...

Review and troubleshoot import errors - Knowledge Base

Below, learn how to resolve errors detected during an import, download an error file, view error details, and correct issues in your import...