Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
excalibur-router
Advanced tools
A scene router for Excalibur.
npm install excalibur-router
import * as ex from 'excalibur'
import { Router } from 'excalibur-router'
const engine = new ex.Engine({
width: 800,
height: 600,
})
class Level1 extends ex.Scene {}
class Level2 extends ex.Scene {}
const router = new Router({
routes: {
level1: Level1,
level2: Level2,
},
})
router.start(engine).then(() => {
router.goto('level1')
})
Router repurposes Loaders to act as scenes. Resources can be loaded using router.addResource(resources)
and they will be loaded automatically during scene navigation.
When loading, the router temporarily navigates to the loading scene and continues to the target once loading has completed. Router has a default loading scene, but you can provide your own:
class LoadingScene extends ex.Scene {
// if true, navigation will not resume until this scene emits a 'complete' event
// it is false by default
defer = false
onLoadStart() {}
onLoad(progress: number) {}
onLoadComplete() {
// if this.defer is true:
this.emit('complete', undefined)
}
}
const router = new Router({
routes: {...},
loader: LoadingScene,
})
You can have multiple loaders as well:
const router = new Router({
routes: {...},
loader: {
boot: BootLoadingScene,
// default will be used if no loader is provided in router.goto()
default: LoadingScene
},
})
router.goto('level1', {
loader: 'boot'
})
Scenes can be imported dynamically as routes, which will then trigger a loading scene when navigated to. If these scenes contain any router.addResource()
calls or import files that do, they will get loaded in the same loading screen.
import * as ex from 'excalibur'
import { Router } from 'excalibur-router'
const engine = new ex.Engine({
width: 800,
height: 600,
})
const router = new Router({
routes: {
level1: () => import('./level1'), // contains default export of scene
level2: () => import('./level2'),
},
})
router.start(engine).then(() => {
router.goto('level1')
})
Transitions are actors with lifecycle hooks for the transitioning of scenes. They typically will play the outro, be carried into the next scene, play their intro, and then be killed.
import { Transition, TransitionArgs } from 'excalibur-router'
export class FadeTransition extends Transition {
el: ScreenElement
constructor(args: TransitionArgs = {}) {
super({
duration: 300,
z: Infinity,
...args,
})
}
onInitialize(engine: Engine): void {
this.el = new ScreenElement({
x: 0,
y: 0,
z: this.z,
width: engine.canvasWidth,
height: engine.canvasHeight,
color: Color.Black,
})
this.el.graphics.opacity = this.isOutro ? 0 : 1
this.addChild(this.el)
}
onIntroStart() {
this.el.graphics.opacity = 1
}
onOutroStart() {
this.el.graphics.opacity = 0
}
onIntro(progress: number) {
this.el.graphics.opacity = 1 - progress
}
onOutro(progress: number) {
this.el.graphics.opacity = progress
}
}
They can be used in router.goto
router.goto('level1', {
transition: new FadeTransition(),
})
There are some default transition effects provided:
Depending on the transition effect, you may want the transition to carry into a loading scene. Transitions can take persistOnLoading
argument to do this, causing the effect to stay in its completed "outro" state for the entirety of the loading scene.
Note This does not apply for the initial loading scene
router.goto('level1', {
transition: new FadeTransition({
persistOnLoading: true,
}),
})
You can also provide a number value instead, which will persist the transition for that amount of time in ms before "introing" into the loading scene. This is useful for something like a Fade effect, where you might want to stay faded unless the loading is taking a long time.
router.goto('level1', {
transition: new FadeTransition({
// if loading takes longer than 200ms, fade back in to show loading scene
persistOnLoading: 200,
}),
})
See the examples for detailed usage.
FAQs
A scene router for Excaliburjs
The npm package excalibur-router receives a total of 1 weekly downloads. As such, excalibur-router popularity was classified as not popular.
We found that excalibur-router demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.