exposify

v0.5.0

browserify transform that exposes globals added via a script tag as modules so they can be required. For more information about how to use this package see README

Latest version published 10 years ago

License: MIT

Package Health Score

54 / 100

security
No known security issues
popularity
Recognized
maintenance
Inactive
community
Limited

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
0.5.0	\|	10/2015	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.4.3	\|	06/2015		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.3.0	\|	01/2015		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.1.5	\|	01/2015		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.2.0	\|	06/2014		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Recognized

Weekly Downloads (35,834)

GitHub Stars: 63
Forks: 10
Contributors: -

Direct Usage Popularity

The npm package exposify receives a total of 35,834 downloads a week. As such, we scored exposify popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package exposify, we found that it has been starred 63 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 0
Funding: Yes

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like exposify is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 0
Open PR: 1
Last Release: 10 years ago
Last Commit: 10 years ago

Further analysis of the maintenance status of exposify based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for exposify is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 12 years
Dependencies: 5 Direct
Versions: 14
Install Size: 0 B
Dist-tags: 1
# of Files: 0
Maintainers: 2
TS Typings: No

exposify has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

exposify

browserify transform that exposes globals added via a script tag as modules so they can be required.



  
  
  [..]

// main.js
var $ = require('jquery')
  , THREE = require('three')

console.log('THREE revision: ', THREE.REVISION);
console.log('jquery version: ', $().jquery);

Building via JavaScript

var browserify = require('browserify');

// configure what we want to expose
var exposeConfig = { expose: { jquery: '$', three: 'THREE' } };

browserify()
  .require(require.resolve('./main'), { entry: true })
  .transform('exposify', exposeConfig)
  .bundle({ debug: true })
  .pipe(fs.createWriteStream(path.join(__dirname, 'bundle.js'), 'utf8'))

Building via Commandline

Using the EXPOSIFY_CONFIG environment variable:

EXPOSIFY_CONFIG='{ "jquery": "$", "three": "THREE" }' browserify --debug -t exposify main.js &gt; bundle.js

Or using a Browserify transform option:

browserify --debug -t [ exposify --expose [ --jquery $ --three THREE ] ] main.js &gt; bundle.js

Or use browserify-shim which can configure exposify in package.json among other features.

Installation

npm install exposify

API

exposify::config

The config which is used by exposify to determine which require statemtents to replace and how. You need to set this or provide it via the EXPOSIFY_CONFIG environment variable.

 var b = browserify();
// setting via transform argument
b.transform('exposify', { expose: { jquery: '$', three: 'THREE' } });

 // setting from javascript
exposify.config = { jquery: '$', three: 'THREE' };

 # setting from command line
EXPOSIFY_CONFIG='{ "jquery": "$", "three": "THREE" }' browserify -t exposify ...

Source:

index.js , lineno 33

exposify::expose

Exposes the expose function that operates on a string

Source:

index.js , lineno 78

exposify::filePattern

Regex pattern of files whose content is exposified

Source:

index.js , lineno 71

exposify(file, opts) → {TransformStream}

browserify transform which exposes globals as modules that can be required.

Parameters:

Name	Type	Argument	Description
`file`	string		file whose content is to be transformed
`opts`	Object	<optional>	(exposify config), defaults to exposify.config or $EXPOSIFY_CONFIG

Source:

index.js , lineno 9

Returns:

transform that replaces require statements found in the code with global assigments

Type: TransformStream

generated with docme

License

MIT

exposify dependencies

globo map-obj replace-requires through2 transformify

exposify development dependencies

FAQs

What is exposify?

browserify transform that exposes globals added via a script tag as modules so they can be required. Visit Snyk Advisor to see a full health score report for exposify, including popularity, security, maintenance & community analysis.

Is exposify popular?

The npm package exposify receives a total of 35,834 weekly downloads. As such, exposify popularity was classified as a recognized. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is exposify well maintained?

We found indications that exposify is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is exposify safe to use?

The npm package exposify was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 4 December-2025, at 16:10 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected