dead-by-daylight
Advanced tools
Some structured Dead by Daylight data.
npm install --save dead-by-daylight@^1.30.0
yarn add dead-by-daylight@^1.30.0
(if configured properly)
npm install --save @jaid/dead-by-daylight@^1.30.0
import deadByDaylight from "dead-by-daylight"
const result = deadByDaylight.perks.hauntedGround
Variable result will be:
{
id: "hauntedGround",
title: "Hex: Haunted Ground",
iconId: "hauntedGround",
owner: "spirit",
rarity: "veryRare",
for: "killer",
level: 35,
iconPath: "UI/Icons/Perks/Haiti/iconPerks_hauntedGround.png",
visible: true,
released: true,
}
Contains official Dead by Daylight content copied from the Steam release. Copyright by Behaviour Interactive.
Setting up:
git clone git@github.com:jaid/dead-by-daylight.git
cd dead-by-daylight
npm install
Testing:
npm run test:dev
Testing in production environment:
npm run test
MIT License
Copyright © 2020, Jaid <jaid.jsx@gmail.com> (https://github.com/jaid)
FAQs
Some structured Dead by Daylight data.
The npm package dead-by-daylight receives a total of 68 weekly downloads. As such, dead-by-daylight popularity was classified as not popular.
We found that dead-by-daylight 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
Five malicious NuGet packages impersonate Chinese .NET libraries to deploy a stealer targeting browser credentials, crypto wallets, SSH keys, and local files.
Security News
pnpm 11 turns on a 1-day Minimum Release Age and blocks exotic subdeps by default, adding safeguards against fast-moving supply chain attacks.
Security News
The remediated findings include organization permission bugs, stale project access after transfers, OIDC replay edge cases, audit logging gaps, and an IDOR in API token deletion.