question-mark

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.

Route Fails on Navigation

See original GitHub issue

Issue Description

Uncaught (in promise) TypeError: Cannot read property 'c' of undefined
    at transition_out (index.mjs:751)

Seems like it’s having an issue with this. Not sure if this transition_out is Svelte itself or it is tinro, but it seems to only effect the route when changed client side by clicking a link or using a goto. If you are refreshing the page, the route works just fine.

function transition_out(block, local, detach, callback) {
    if (block && block.o) {
        if (outroing.has(block))
            return;
        outroing.add(block);
        outros.c.push(() => {
            outroing.delete(block);
            if (callback) {
                if (detach)
                    block.d(1);
                callback();
            }
        });
        block.o(local);
    }
}

I realize this might be an odd bug and looks like a possible Svelte issue itself, https://github.com/sveltejs/svelte/issues/3165

Just wanted to let you know this is happening feel free to close.

    "svelte": "^3.22.2",
   "tinro": "^0.2.7"

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
stolinskicommented, May 19, 2020

Perfect. Works as expected. Thank you for your help.

1reaction
AlexxNBcommented, May 19, 2020

Let’s try to import this way:

// import {Route} from 'tinro';
import {Route} from 'tinro/cmp/index.js';
Read more comments on GitHub >

github_iconTop Results From Across the Web

Waiting for the result of a Navigation - Vue Router
Navigation Failures are Error instances with a few extra properties that gives us enough ... In all cases, to and from are normalized...
Read more >
Route Calculation Error When Attempting to Navigate to a ...
A route calculation error, stating that the maps do not have routable roads, can appear when the routing settings of a device are...
Read more >
Route did not calculate due to an error message - Manula.com
One possible error you may encounter is Route calculation failed: Download missing map. This error occurs when you are creating a route between...
Read more >
angular 10 routing & navigation error with parameter
Id]" it's working but when I am using "router.navigate" it naviagte first route exam-panel with parmeter ok, then automatically route to ...
Read more >
Router can't navigate when exception occurrs #15946 - GitHub
Navigate fails to navigate when exception occurs. Expected behavior. Router is able to navigate even though application exception occurred
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found