Skip to content

Licensing for this library #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Mikerah opened this issue Jan 7, 2019 · 2 comments
Closed

Licensing for this library #2

Mikerah opened this issue Jan 7, 2019 · 2 comments

Comments

@Mikerah
Copy link
Contributor

Mikerah commented Jan 7, 2019

Since the eventual goal of this library is to be used within the Libp2p js project, this library should be licensed under the MIT License. All Libp2p repositories are licensed under this license.

Also, since there is a lot of intersection between the gossipsub protocols and floodsub protocols, it is going to be easier to use open-sourced components in order to build out this library.

@Mikerah
Copy link
Contributor Author

Mikerah commented Jan 7, 2019

Thoughts @ChainSafe and @GregTheGreek?

@ChainSafeSystems
Copy link
Member

SGTM!

fryorcraken pushed a commit to fryorcraken/js-libp2p-gossipsub that referenced this issue Aug 2, 2022
tysonclugg added a commit to tysonclugg/js-libp2p-gossipsub that referenced this issue Apr 17, 2025
The engine spec applied here matches the minimum requirements of all transient dependencies (in `package-lock.json`). The engine requirement is changed from `npm` version to `node` version to better match with the engine spec discovered as outlined in the install attempts below (nobody seems to depend on npm versions, only node version).

With `engine-strict=true` in `.npmrc`, I attempted to install with old versions of node/npm, until successfully installed and tested.

Minimum spec install attempt ChainSafe#1:
```
$ nvm install v18.1.0
v18.1.0 is already installed.
Now using node v18.1.0 (npm v8.8.0)
$ npm install
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: @semantic-release/[email protected]
npm ERR! notsup Not compatible with your version of node/npm: @semantic-release/[email protected]
npm ERR! notsup Required: {"node":">=20.8.1"}
npm ERR! notsup Actual:   {"npm":"8.8.0","node":"v18.1.0"}
```

Minimum spec install attempt ChainSafe#2:
```
$ nvm install v20.8.1
v20.8.1 is already installed.
Now using node v20.8.1 (npm v10.1.0)
$ npm install
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: [email protected]
npm ERR! notsup Not compatible with your version of node/npm: [email protected]
npm ERR! notsup Required: {"node":"^18.18.0 || ^20.9.0 || >=21.1.0"}
npm ERR! notsup Actual:   {"npm":"10.1.0","node":"v20.8.1"}
```

Minimum spec install attempt ChainSafe#3:
```
$ nvm install v20.9.0
v20.9.0 is already installed.
Now using node v20.9.0 (npm v10.1.0)
$ npm install
npm WARN deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead
npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported

> @chainsafe/[email protected] prepare
> npm run build

> @chainsafe/[email protected] build
> aegir build

[10:23:50] tsc [started]
[10:23:52] tsc [completed]
[10:23:52] esbuild [started]
[10:23:52] esbuild [completed]

added 219 packages, removed 312 packages, changed 607 packages, and audited 1896 packages in 14s

363 packages are looking for funding
  run `npm fund` for details

17 vulnerabilities (16 moderate, 1 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
```

BREAKING CHANGE: Requires Node v20.9.0 or newer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants