Installations

npm install @types/filing-cabinet

Developer Guide

BETA

Typescript

Yes

Module System

N/A

Score

71.3

Supply Chain

89.3

Quality

75.3

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

150

Total

61,817

Closed

9,749

Merged

51,918

Issues

Open

565

Total

8,085

Closed

7,520

Releases

1

0.1.450

Updated on Sep 04, 2019

View All 1 releases

Languages

3

TypeScript

JavaScript

Shell

TypeScript (99.84%)

JavaScript (0.15%)

Shell (0.01%)

Developer

DefinitelyTyped

Download Statistics

Total Downloads

0

Last Day

0

Last Week

0

Last Month

0

Last Year

0

GitHub Statistics

NOASSERTION License

50,028 Stars

89,737 Commits

30,433 Forks

640 Watchers

6 Branches

9,957 Contributors

Updated on Jul 13, 2025

Maintainers

1

View All 9,957 Contributors

Package Meta Information

Latest Version

2.5.3

Package Id

@types/filing-cabinet@2.5.3

Unpacked Size

6.42 kB

Size

2.21 kB

File Count

5

Published on

Nov 07, 2023

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

0%

NaN

Compared to previous day

Last Week

0%

NaN

Compared to previous week

Last Month

0%

NaN

Compared to previous month

Last Year

0%

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Installation

npm install --save @types/filing-cabinet

Summary

This package contains type definitions for filing-cabinet (https://github.com/mrjoelkemp/node-filing-cabinet).

Details

Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/filing-cabinet.

index.d.ts

1declare namespace cabinet {
2    interface Options {
3        /** the dependency path */
4        partial: string;
5        /** the path to all files */
6        directory: string;
7        /** the path to the file containing the partial */
8        filename: string;
9        /**
10         * the parsed AST for filename
11         * Useful optimization for avoiding a parse of filename
12         */
13        ast?: any;
14        /**
15         * `requirejs` config for resolving aliased JavaScript modules
16         */
17        config?: any;
18        /**
19         * `webpack` config for resolving aliased JavaScript modules
20         */
21        webpackConfig?: any;
22        /**
23         * config for resolving entry file for `node_modules`.
24         * This value overrides the main attribute in the `package.json` file;
25         * used in conjunction with the `packageFilter` of the resolve package
26         */
27        nodeModulesConfig?: any;
28        /**
29         * Path to a typescript configuration.
30         * Could also be an object representing a pre-parsed typescript config
31         */
32        tsConfig?: string | object | undefined;
33        /**
34         * For typescript files, whether to prefer *.js over *.d.ts
35         */
36        noTypeDefinitions?: boolean | undefined;
37    }
38
39    type Resolver = (partial: string, filename: string, directory: string, config?: any) => void;
40
41    /**
42     * Register a custom lookup resolver for a file extension
43     * If a given extension does not have a registered resolver,
44     * cabinet will use a generic file resolver which is basically `require('path').join`
45     * with a bit of extension defaulting logic
46     * @param extension the extension of the file that should use the custom resolver (ex: '.py', '.php')
47     * @param resolver  A resolver of partial paths
48     */
49    function register(extension: string, resolver: Resolver): void;
50}
51
52declare function cabinet(options: cabinet.Options): string;
53
54export = cabinet;
55

Additional Details

Last updated: Tue, 07 Nov 2023 03:09:37 GMT
Dependencies: none

Credits

These definitions were written by Piotr Błażejewicz (Peter Blazejewicz).

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Security-Policy

Determines if the project has published a security policy.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

9

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

9

License

Determines if the project has defined a license.

8

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

SAST

Determines if the project uses static code analysis.

0

Fuzzing

Determines if the project uses fuzzing.

Score

7

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More