Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

IPFS dependencies giving warnings #2225

Closed
mitra42 opened this issue Jul 5, 2019 · 3 comments · Fixed by #2242
Closed

IPFS dependencies giving warnings #2225

mitra42 opened this issue Jul 5, 2019 · 3 comments · Fixed by #2242
Labels
exp/novice Someone with a little familiarity can pick up kind/bug A bug in existing code (including security flaws) P4 Very low priority status/ready Ready to be worked

Comments

@mitra42
Copy link

mitra42 commented Jul 5, 2019

  • Version: 0.36.4
  • Platform: Multiple
  • Subsystem: Dependencies

Type: Bug

Severity: Low

Description:

During installation or yarn upgrade IPFS is generating warnings about deprecated versions.
Specifically ...

ipfs > boom@7.3.0: This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.

Everything seems to work though when people are installing library, then real problems are getting masked by the warnings.

Steps to reproduce the error:

yarn upgrade in any application that has a dependency on IPFS.
@alanshaw
Copy link
Member

@achingbrain @vasco-santos the offending modules are ipfs-mfs and ipfs-multipart - would you mind updating deps so we don't get these warnings?

@alanshaw alanshaw added kind/bug A bug in existing code (including security flaws) exp/novice Someone with a little familiarity can pick up P4 Very low priority status/ready Ready to be worked labels Jul 10, 2019
@vasco-santos
Copy link
Member

ipfs-multipart is using a commit from the deprecated ipfs-api. Anyone knows why that is happening?

@alanshaw
Copy link
Member

alanshaw commented Jul 10, 2019 •
edited
Loading

3 years ago, could probably do with some updates ipfs-inactive/js-ipfs-multipart@0d71ecc

Apologies @vasco-santos I meant to tag @hugomrdias not you!

@alanshaw alanshaw mentioned this issue Jul 12, 2019
Merged
alanshaw added a commit to ipfs-inactive/js-ipfs-multipart that referenced this issue Jul 12, 2019
@alanshaw
They moved to @hapi namespace and now spew warnings on npm install.
d9b824e 
refs ipfs/js-ipfs#2225

License: MIT
Signed-off-by: Alan Shaw <alan.shaw@protocol.ai>
alanshaw added a commit to ipfs-inactive/js-ipfs-multipart that referenced this issue Jul 12, 2019
@alanshaw
chore: update hapi deps
7a949d1 
They moved to `@hapi` namespace and now spew warnings on npm install.

refs ipfs/js-ipfs#2225

License: MIT
Signed-off-by: Alan Shaw <alan.shaw@protocol.ai>
@alanshaw alanshaw mentioned this issue Jul 12, 2019
Merged
alanshaw added a commit that referenced this issue Jul 12, 2019
@alanshaw
chore: update deps
3a2a7eb 
resolves #2225

License: MIT
Signed-off-by: Alan Shaw <alan.shaw@protocol.ai>
@alanshaw alanshaw mentioned this issue Jul 12, 2019
Merged
alanshaw added a commit that referenced this issue Jul 12, 2019
@alanshaw
chore: update deps (#2242)
04aa63c 
resolves #2225

License: MIT
Signed-off-by: Alan Shaw <alan.shaw@protocol.ai>
hugomrdias pushed a commit to ipfs-inactive/js-ipfs-multipart that referenced this issue Jul 12, 2019
@alanshaw @hugomrdias
chore: update hapi deps (#15)
f41c646 
They moved to `@hapi` namespace and now spew warnings on npm install.

refs ipfs/js-ipfs#2225

License: MIT
Signed-off-by: Alan Shaw <alan.shaw@protocol.ai>
@mitra42 mitra42 mentioned this issue Aug 2, 2019
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
exp/novice Someone with a little familiarity can pick up kind/bug A bug in existing code (including security flaws) P4 Very low priority status/ready Ready to be worked
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: update deps ipfs/js-ipfs
3 participants
@alanshaw @mitra42 @vasco-santos