Issue with notFound never triggered

I have a simple route like:

router
  .on({
    '/product/:id': function (params) {
      renderProduct(params.id)
    },
    '/':function() {
      renderStartpage();
    }
  })
  .notFound(function() {
    pageNotFoundController();
  });

If the URL is / it will go to start page. Also if the URL is /foobar. I can never seem to be triggering the pageNotFoundController().

How should I configure my routes differently? Naturally I only want to valid routes: / and /product/XX.

[nordskill]

I guess I’ve found a workaround for this issue:

router.on(function () {
   if (window.location.pathname.length > 1) {
    console.log('404');
   } else {
    console.log('home');
   }
}).resolve();

[johnhult]

@krasimir I changed the position of the / to the end instead but nothing really changed. Said two different things in the README.md, so I thought it didn’t matter 😃 I have the latest npm version of navigo so that should be okay.

What happens is that if I go to /asdf (i.e. a non-existing route) it will just load the /asdf route as the root route instead. If I then try to navigate to for example /work, it will instead go to /asdf/work.

I was wondering if it could have something to do with my gulptask if it isn’t Navigo itself?

	gulp.task('express', function() {
		var express = require('express');
		app = express();
		app.use(historyApiFallback());
		app.use(require('connect-livereload')({port: 4001}));
		app.use(express.static(__dirname));
		app.listen(4000);
	});