1.0.0 • Published 2 years ago

muban-page-transition-controller v1.0.0

Weekly downloads
-
License
MIT
Repository
github
Last release
2 years ago

Muban Page Transition Controller

npm bundle size npm bundle size npm

This library enables you to add page transitions to a Muban project.

Getting Started

Installing

yarn add muban-page-transition-controller

Init in App component

To initialise the component in your project you first have to create a variable that can contain the controller.

IMPORTANT: Do not add the controller variable as property to App component class

Use a let instead outside your class because the App component gets reinitialised when your new page is rendered, this can lead to a duplication of event listeners which can result into unexpected behaviour.

Set the value as null because the controller needs to be initialised asynchronous.

Example:

import { PageTransitionController } from 'muban-page-transition-controller';
import AbstractComponent from '../../AbstractComponent';

export let pageTransitionController: PageTransitionController | null = null;

export default class App extends AbstractComponent {
 public static readonly displayName: string = 'app-root';

 // eslint-disable-next-line no-useless-constructor
 public constructor(element: HTMLElement) {
   super(element);

   // for generic app logic
 }

 public dispose() {
   // clean up stuff when hot reloading
   super.dispose();
 }
}

With the variable in place we can use the initialisePageTransitions function. Do this in an async adopted function on your App class, for example:

import {
  initialisePageTransitions,
  PageTransitionController,
} from 'muban-page-transition-controller';
import AbstractComponent from '../../AbstractComponent';
import TransitionComponent from '../../general/transition-component/TransitionComponent';

export let pageTransitionController: PageTransitionController | null = null;

export default class App extends AbstractComponent {
  public static readonly displayName: string = 'app-root';

  // eslint-disable-next-line no-useless-constructor
  public constructor(element: HTMLElement) {
    super(element);

    // for generic app logic
  }

  public async adopted(): Promise<void> {
    if (!pageTransitionController) {
      pageTransitionController = await initialisePageTransitions<TransitionComponent>({
        linkElements: this.getElements<HTMLAnchorElement>('a'),
      });
    }
  }

  public dispose() {
    // clean up stuff when hot reloading
    super.dispose();
  }
}

The initialisePageTransitions function expects the following options:

keydescriptiontyperequired
linkElementsThe link elements that you want the page transition to trigger onArray<HTMLAnchorElement>true
renderModeThe selected render mode. browser mode is the default value and utilizes the default browser navigation. Slower because the new page fetch can only start until the transition is complete but it's safer to run in environments where advanced external scripts need to be executed. dynamic renders the new page in the same DOM without leaving the page. Use with caution as it only replaces the app-root in the DOM and doesn't executes advanced external scripts again.browser/dynamicbrowser
onNavigationCompleteA callback that triggers when the navigation to a new page is finished, including the animationsfunctionfalse
onNavigationCompleteA callback that triggers when the navigation to a new page is finished, including the animationsfunctionfalse

Updating link elements

When the renderMode is set to dynamic the whole DOM changes when you navigated to a new page you need to update the supplied link elements to the new links on the page. Utilize the onNavigationComplete for this and the updateLinkElements function which accepts the controller and the new linkElements as an argument, for example:

import {
  initialisePageTransitions,
  PageTransitionController,
  updateLinkElements,
} from 'muban-page-transition-controller';
import AbstractComponent from '../../AbstractComponent';
import TransitionComponent from '../../general/transition-component/TransitionComponent';

export let pageTransitionController: PageTransitionController<TransitionComponent> | null = null;

export default class App extends AbstractComponent {
  public static readonly displayName: string = 'app-root';

  // eslint-disable-next-line no-useless-constructor
  public constructor(element: HTMLElement) {
    super(element);

    // for generic app logic
  }

  public async adopted(): Promise<void> {
    if (!pageTransitionController) {
      pageTransitionController = await initialisePageTransitions<TransitionComponent>({
        linkElements: this.getElements<HTMLAnchorElement>('a'),
        transitionComponentSelector: `[data-component="${TransitionComponent.displayName}"]`,
        onNavigationComplete: () => {
          if (!pageTransitionController) return;
          updateLinkElements(pageTransitionController, this.getElements<HTMLAnchorElement>('a'));
        },
      });
    }
  }

  public dispose() {
    // clean up stuff when hot reloading
    super.dispose();
  }
}

Programmatically navigate to another page

You can also programmatically to another page using the navigateTo function.

The function expects the following arguments:

argumentdescriptiontyperequireddefault
controllerThe controller you currently use in your applicationPageTransitionControllertrue
urlThe new url you want to navigate tourl (string)true
updatePushStateUpdate the history of the browser session. Will update the page URL and allow navigation with back/forward button. IMPORTANT: only supply false if you know what you are doing, in most cases it will break user expected behaviour.booleanfalsetrue

Disposing the controller

If you don't need your controller anymore, it's important to dispose it, this will remove all active event listeners.

pageTransitionController.disposableManager.dispose();
pageTransitionController = null;