npmpackage.info

@types/parse-conflict-json

The repository for high quality TypeScript type definitions.

1.1.3

49,098

NOASSERTION

TypeScript

5.17 kB

264,630 7

Installations

npm install @types/parse-conflict-json

Developer Guide

BETA

Typescript

Yes

Module System

N/A

Score

66.9

Supply Chain

76.4

Quality

75.3

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

159

Total

60,617

Closed

9,563

Merged

50,895

Issues

Open

560

Total

8,070

Closed

7,510

Releases

0.1.450

Published on 04 Sept 2019

View all 1 releases

Contributors

9,977

View all 9,977 contributors

Languages

TypeScript

JavaScript

Shell

TypeScript (99.9%)

JavaScript (0.09%)

Shell (0.01%)

Developer

DefinitelyTyped

Download Statistics

Total Downloads

264,630

Last Day

109

Last Week

667

Last Month

2,773

Last Year

38,168

GitHub Statistics

49,098 Stars

88,626 Commits

30,291 Forks

640 Watching

5 Branches

9,977 Contributors

Maintainers

Package Meta Information

Latest Version

1.1.3

Package Id

@types/parse-conflict-json@1.1.3

Unpacked Size

5.17 kB

Size

2.13 kB

File Count

Publised On

07 Nov 2023

Total Downloads

Cumulative downloads

Total Downloads

264,630

Last day

-24.8%

109

Compared to previous day

Last week

-6.3%

667

Compared to previous week

Last month

2.8%

2,773

Compared to previous month

Last year

-23.7%

38,168

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@types/node

Versions

Installation

npm install --save @types/parse-conflict-json

Summary

This package contains type definitions for parse-conflict-json (https://github.com/npm/parse-conflict-json#readme).

Details

Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/parse-conflict-json.

index.d.ts

1/// <reference types="node" />
2
3/**
4 * Parse a JSON string that has git merge conflicts, resolving if possible.
5 * If the JSON is valid, it just does JSON.parse as normal.
6 * If either side of the conflict is invalid JSON, then an error is thrown for that.
7 */
8declare function parseConflictJSON(
9    text: string,
10    reviver?: (this: any, key: string, value: any) => any,
11    prefer?: parseConflictJSON.Prefer,
12): any;
13
14declare namespace parseConflictJSON {
15    /**
16     * returns true if the data looks like a conflicted diff file
17     */
18    function isDiff(text: string): boolean;
19
20    /**
21     * If prefer is set to theirs, then the vaules of theirs and ours are switched in the resolver function.
22     * (Ie, we'll apply their changes on top of our object, rather than the other way around.)
23     * Parse the conflicted file into 3 pieces: ours, theirs, and parent
24     * Get the diff from parent to ours.
25     * Apply each change of that diff to theirs.
26     * If any change in the diff set cannot be applied (ie, because they changed an object into a non-object and we changed a field on that object),
27     * then replace the object at the specified path with the object at the path in ours.
28     */
29    type Prefer = "theirs" | "ours";
30}
31
32export = parseConflictJSON;
33

Additional Details

Last updated: Tue, 07 Nov 2023 09:09:39 GMT
Dependencies: @types/node

Credits

These definitions were written by Piotr Błażejewicz.

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Dangerous-Workflow

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

10

Security-Policy

Determines if the project has published a security policy.

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-01-27

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

Other packages similar to @types/parse-conflict-json

@wemnyelezxnpm/soluta-eaque-minus

1.0.0

Turns off all rules that are unnecessary or might conflict with [Prettier].