# can-namespace

> Namespace where can-* packages are registered

Latest version **1.0.0** (published 2016-12-13) · 0 weekly downloads

## Install

```sh
npm install can-namespace
pnpm add can-namespace
yarn add can-namespace
bun add can-namespace
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.0 |
| Published | 2016-12-13 |
| First published | 2016-12-13 |
| Weekly downloads | 0 |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 1 |
| Author | Bitovi |
| Maintainers | phillipskevin |
| Keywords | canjs, canjs-plugin, donejs |

## Links

- npm: https://www.npmjs.com/package/can-namespace
- Repository: https://github.com/canjs/can-namespace
- Homepage: http://canjs.com
- Issues: https://github.com/canjs/can-namespace/issues
- npm.io page: https://npm.io/package/can-namespace

## Recent versions

- 1.0.0 (latest) — 2016-12-13

## README

# can-namespace

Namespace where can-* packages are registered

## Usage

`can-namespace` exports an object that can be used to ensure only one version of a module is loaded in an app.

For example, if you have a module `can-unicorn` that you want to make sure is only loaded a single time, you can use `can-namespace`:

```js
var namespace = require('can-namespace');

var unicorn = {
	// ...
};

if (namespace.unicorn) {
	throw new Error("You can't have two versions of can-unicorn, check your dependencies");
} else {
	module.exports = namespace.unicorn = unicorn;
}
```

Any module requiring `can-namespace` will receive the same module because only one version of `can-namespace` will ever be published.

---
_Source: https://npm.io/package/can-namespace · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._