npmpackage.info

Gathering detailed insights and metrics for git-loader

Other packages similar to git-loader

@graphql-tools/git-loader

8.0.24

A set of utils for faster development of GraphQL tools

@graphql-toolkit/git-loader

0.10.7

A set of utils for faster development of GraphQL tools

@cz-git/loader

1.11.1

commitizen and commitlint configure loader for cz-git

@graphql-inspector/git-loader

5.0.1

Load GraphQL Schema and Documents from Git repository

Gathering detailed insights and metrics for git-loader

git-loader - 1.0.0 | npmpackage.info

git-loader

a basic commonjs require mod to allow access to git version of module 🛍️

1.0.0

JavaScript

680.00 B

527 1.3

Installations

npm install git-loader

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

12.16.3

NPM Version

6.14.4 Score

70.3

Supply Chain

80.8

Quality

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

6

Total

11

Closed

0

Merged

5

Issues

Open

5

Total

6

Closed

1

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

tetedacier

Download Statistics

Total Downloads

527

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

45 Commits

1 Watchers

8 Branches

1 Contributors

Updated on May 17, 2020

Bundle Size

1.44 kB

Minified

680.00 B

Minified + Gzipped

Bundlephobia

Maintainers

View All 1 Contributors

Package Meta Information

Latest Version

1.0.0

Package Id

git-loader@1.0.0

Unpacked Size

12.46 kB

Size

4.33 kB

File Count

NPM Version

6.14.4

Node Version

12.16.3

Total Downloads

Cumulative downloads

Total Downloads

527

Last Day

Compared to previous day

Last Week

-75%

Compared to previous week

Last Month

100%

Compared to previous month

Last Year

-8.7%

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

commitizen cz-conventional-changelog husky tap

git-loader

This module provide the ability to require a commonjs module at a given version in the repository history.

This may be usefull to monitor performance enhancement during a refactor or avoiding the use of submodule pointing at other branch of the same repository.

git bisect command can provide the same kind of feature, but I wanted to play with git and module override.

Usage

This module must be installed as a devDependencies since it won't and should'nt be of any use on production servers. Which means you should install it using npm install --save-dev git-loader and use it in ci or local environment like this

1require('git-loader')
2const previousVersionOfModuleA = './A#previous-tag.git'
3const currentVersionOfModuleA = './A'
4
5// ... do your stuff
6

You can also run the same using node -r git-loader perf.js where perf.js looks like

1const previousVersionOfModuleA = './A#previous-tag.git'
2const currentVersionOfModuleA = './A'
3
4// ... do your stuff
5

Moreover this module needs git to be installed in the environment you will on which you will use it, but there's a a lot of chance this may be the case, since it seems to be one of the npm requirement to enable some of its feature like git dependencies. (note for myself, I may have use the npm's internal git lib instead of writing my own ...)

Tooling and commit on this project

This package makes use of the commitizen and husky packages, see how to install it on you project and how to use it.

Roadmap

All the roadmap for this project is handled using github features like the github's projects page, milestone, issues ... to be honest I'm still wondering what will be the most efficient way of handling it.

Warnings

One of the strongest limitation of this module is that when a scripts is loaded at a given version, it could require other modules which exists in your project at this specific revision.

Those modules may not exist at the current point of history of the working folder and even if they still exists they may exports a different signature.

Same is true for the dependencies defined in your package files.

All those limitation has been clearly identified and may be addressed or not in future versions.

No vulnerabilities found.

10

Binary-Artifacts

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

0

Code-Review

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

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

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

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

License

Determines if the project has defined a license.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

1.3

/10

Last Scanned on 2025-06-23

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