slynova-org / flydrive Goto Github PK
View Code? Open in Web Editor NEW☁️ Flexible and Fluent framework-agnostic driver based system to manage storage in Node.js
License: MIT License
☁️ Flexible and Fluent framework-agnostic driver based system to manage storage in Node.js
License: MIT License
Hi
May i know ehen the FTP driver will be avilable for adonis js framework because of i need it ...
Thanks ..
I am planning about using this in real project. Is it enough stable to use in production environment? Is development still active?
Thanks!
Branch | Build failing 🚨 |
---|---|
Dependency | nyc |
Current Version | 11.7.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
nyc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
2.339.0
to 2.340.0
.This version is covered by your current version range and after updating it in your project the build failed.
aws-sdk is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
See changelog for more information.
The new version differs by 5 commits.
083e7a6
Updates SDK to v2.340.0
3714284
Client side monitoring functional tests (#2316)
4d6aa8b
Merge pull request #2314 from srchase/cloudfront-signer-documentation
eceed60
Update lib/cloudfront/signer.js
8c832b0
improved documentation for #2308
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
It will be really good if you could add a drvier for google drive, or perhaps add a section in the doc explaining how to add driver !
Thank you
Will it be supported for google cloud storage?
TypeError: Cannot read property 'code' of null at Response.s3.headObject (/usr/src/app/node_modules/@slynova/flydrive/src/Drivers/AwsS3.js:34:16) at Request.<anonymous> (/usr/src/app/node_modules/aws-sdk/lib/request.js:364:18) at Request.callListeners (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:105:20) at Request.emit (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:77:10) at Request.emit (/usr/src/app/node_modules/aws-sdk/lib/request.js:683:14) at Request.transition (/usr/src/app/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/usr/src/app/node_modules/aws-sdk/lib/state_machine.js:14:12) at /usr/src/app/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/usr/src/app/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/usr/src/app/node_modules/aws-sdk/lib/request.js:685:12) at Request.callListeners (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:115:18) at Request.emit (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:77:10) at Request.emit (/usr/src/app/node_modules/aws-sdk/lib/request.js:683:14) at Request.transition (/usr/src/app/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/usr/src/app/node_modules/aws-sdk/lib/state_machine.js:14:12) at /usr/src/app/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/usr/src/app/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/usr/src/app/node_modules/aws-sdk/lib/request.js:685:12) at Request.callListeners (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:115:18) at Request.emit (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:77:10) at Request.emit (/usr/src/app/node_modules/aws-sdk/lib/request.js:683:14) at Request.transition (/usr/src/app/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/usr/src/app/node_modules/aws-sdk/lib/state_machine.js:14:12) at /usr/src/app/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/usr/src/app/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/usr/src/app/node_modules/aws-sdk/lib/request.js:685:12) at Request.callListeners (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:115:18) at Request.emit (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:77:10) at Request.emit (/usr/src/app/node_modules/aws-sdk/lib/request.js:683:14) at Request.transition (/usr/src/app/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/usr/src/app/node_modules/aws-sdk/lib/state_machine.js:14:12) at /usr/src/app/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/usr/src/app/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/usr/src/app/node_modules/aws-sdk/lib/request.js:685:12) at Request.callListeners (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:115:18) at callNextListener (/usr/src/app/node_modules/aws-sdk/lib/sequential_executor.js:95:12) at IncomingMessage.onEnd (/usr/src/app/node_modules/aws-sdk/lib/event_listeners.js:269:13) at emitNone (events.js:110:20) at IncomingMessage.emit (events.js:207:7) at endReadableNT (_stream_readable.js:1059:12) at _combinedTickCallback (internal/process/next_tick.js:138:11) at process._tickDomainCallback (internal/process/next_tick.js:218:9)
Branch | Build failing 🚨 |
---|---|
Dependency | japa |
Current Version | 1.0.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As japa is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
The new version differs by 4 commits .
be74183
Merge branch 'release-1.0.2'
e51248a
chore(release): release 1.0.2
f9db00b
test(cli): add cli tests
3b47016
feat(cli): add cli file to be used for configuring test files
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency |
nyc
|
Current Version | 11.7.3 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
nyc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | aws-sdk |
Current Version | 2.224.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
aws-sdk is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
See changelog for more information.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | aws-sdk |
Current Version | 2.226.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
aws-sdk is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
See changelog for more information.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Hi!
Looking at AwsS3.js
code, I found getUrl
and getSignedUrl
methods but I couldn't find those methods on LocalFileSystem.js
driver. It would be interesting to have a standartized getUrl
method across all drivers.
The local driver should accept a baseUrl
option in its configuration object to determine the base URL to be preppended in the file being acessed. Drivers that don't support acessing the file through a URL could throw an exception.
To pass additional configuration to the getUrl
method (like if the URL should be signed or not or the expiry of link) it could use an options object as a second parameter. Some parameters could be ignored depending on the driver.
x.getUrl("file.jpg", {
signedUrl: true,
expiry: 600
});
If path is not normalized before being passed, and coming from a user, anyone can read any files on the host machine. E.g.
const flydrive = new LocalFileSystem({root: '/var/www/app/images'});
app.get('/image', async (req, res) => {
res.send(await flydrive.getBuffer(req.query.path));
}
Then requesting http://example.com/thumbnail?path=/etc/passwd
or http://example.com/thumbnail?path=../../../../etc/passwd
will return contents of /etc/passwd
LocalFileSystem should treat all paths as relative, and perform normalization before joining root path to file path.
I would like to add support for setting metadata, like Content-Type (as third argument to put
), and include the file metadata along the file content in response from get* methods (Azure returns it anyway, I suspect other storage providers do that too).
I need that in my application, so that our thumbnail service can properly recognize file formats. There are also some security implications if Content-Type of uploaded file must be ignored (as is always set to default value).
I propose adding third argument to put
: put(location: string, content: Buffer | Readable | string, metadata?: FileMetadata)
and extending ContentResponse
to:
export interface ContentResponse<ContentType> extends Response {
content: ContentType;
metadata: FileMetadata;
}
Possibly also aliasing StatResponse to FileMetadata?
What if we could use drivers dynamically, that's to say we can change authenfiticated user in case of FTP, AWS Driver for instance in runtime
Imagine my application need to store data to users ftp, so with the current config object I dont see any way to change the authentification credentials
Would be good if al driver with authentification provides a method with(credentials|config)
so that we can change dynamically configuration object, or maybe the Storage manager provide a way to change the configuration when getting the driver instance in the method disk(name)
Hey,
Im using ESM (https://www.npmjs.com/package/esm) and flydrive, when I try to run it in production I got:
{ /home/ubuntu/www/releases/725cf5a1ff04071eab0a9e12319e8d434b41df29/packages/api/node_modules/@slynova/flydrive/src/Exceptions/index.js:1
DriverNotSupported: Driver __esModule is not supported
at Function.driver (/home/ubuntu/www/releases/725cf5a1ff04071eab0a9e12319e8d434b41df29/packages/api/node_modules/@slynova/flydrive/src/Exceptions/index.js:14:23)
at Object.get (/home/ubuntu/www/releases/725cf5a1ff04071eab0a9e12319e8d434b41df29/packages/api/node_modules/@slynova/flydrive/src/Drivers/index.js:24:35) driver: '__esModule' }
Do you have an idea why?
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing 🚨 |
---|---|
Dependency | aws-sdk |
Current Version | 2.223.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
aws-sdk is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
See changelog for more information.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Currently you can access internal exceptions via:
import * as Exceptions from '@slynova/flydrive/build/Exceptions';
However it feels like these should be available at the top level, e.g:
import { Exceptions } from '@slynova/flydrive';
What do you think? I am happy to do a PR for this if there is interest
2.317.0
to 2.318.0
.This version is covered by your current version range and after updating it in your project the build failed.
aws-sdk is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
See changelog for more information.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Is there any intention to add Backblaze B2 storage driver?
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing 🚨 |
---|---|
Dependency | eslint-plugin-import |
Current Version | 2.10.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 21 commits.
e0dcfbd
Merge branch 'fix-perf' into release-2.10.1 (fixes #1058)
774ea8d
changelog note for #1058
7bd2775
perf: no AST nodes in caches
83c85fc
bump to v2.11.0 for #880 (semver-minor)
54e3013
changelog for #880
0ff8f23
bump to v2.10.1
f0b4f3e
Merge pull request #1069 from ljharb/resolve
fb8e1e5
[patch] use resolve
instead of builtin-modules
d8077c8
Merge pull request #1064 from ljharb/fix_no_cycle
80d1ceb
Merge pull request #1065 from sharmilajesupaul/minor-typo-fix
f13f18e
minor typo in import/no-cycle rule docs
19fc3df
[Fix] no-cycle
: create
must always return an object, even if there’s no listeners
ee15fa4
Merge pull request #880 from futpib/no-commonjs-allow-require
48d0a8a
changelog note for #1046
a2acbde
add fixer for first
(#1046)
There are 21 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
6.1.0
to 6.2.0
.This version is covered by your current version range and after updating it in your project the build failed.
dotenv is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 4 commits.
e1e7d57
6.2.0
1eacd53
add support for preload configuration via env vars (#355)
1f84ba1
add TypeScript types (#345)
194c98e
Fix appveyor repo badge url in readme (#347)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Problem
Returning response.Location
is limiting the app to know only that property of the result.
In cases where you're using different endpoints (for example, switching between s3 and minio servers for development), I'd rather use response.Key
as the reference in DB, and then dynamically set the endpoint depending on the environment.
For example, putObject
is doing it just fine
https://github.com/Slynova-Org/node-flydrive/blob/aea96ae1bc2995a4772391c3dc81682f9f63e500/src/Drivers/AwsS3.js#L163
Also, it could be considered to implement a common response object for all drivers, so you can expect always the same properties depending on which operation has been made, independently of the driver.
For instance: await Drive.put()
could return a response object like
const response = await Drive.disk('s3').put(name, content, params)
response.location // full url (can be empty for local storage)
response.path // same as aws s3 response.Key - /bucket/prefix/file.jpg
response.status // 200
response.response // underlying response object if exists
Branch | Build failing 🚨 |
---|---|
Dependency | aws-sdk |
Current Version | 2.28.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As aws-sdk is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
See changelog for more information.
The new version differs by 8 commits .
18deee0
Updates SDK to v2.29.0
e516ed8
Sync latest version of protocol tests (#1407)
e695c27
Merge pull request #1411 from jeskew/chore/coverage-gap
547e4d8
Add test to make sure all clients can be instantiated
b2016fa
Merge pull request #1406 from jeskew/docs/yard-roundup
88873ea
Correct some yard errors and beef up a few docs
fb50c79
Merge pull request #1398 from jeskew/chore/move-to-codecov
0792e02
Replace coveralls with codecov
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
7.0.0
to 7.0.1
.This version is covered by your current version range and after updating it in your project the build failed.
fs-extra is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 7 commits.
a32c852
7.0.1
6392917
Temporarily disable standard-markdown
ddc1a2f
Fix removeSync() to eliminate spurious ENOTEMPTY errors on Windows (#646)
ab254b1
Added docs/ and CHANGELOG.md to .npmignore (#642) (#643)
287f234
Fix typo in docs (#628)
402c1d0
Show support for mode (#587)
4da17fe
Chore: github issue template (#617)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
2.421.0
to 2.422.0
.This version is covered by your current version range and after updating it in your project the build failed.
aws-sdk is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
See changelog for more information.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Would it possible to support scaleway's object storage, as they follow the S3 api?
Hey, I would love to have support for azure storage. The Azure team recently published a new library https://github.com/Azure/azure-storage-js and it would be great to have this integrated as an alternative to AWS S3.
Branch | Build failing 🚨 |
---|---|
Dependency | aws-sdk |
Current Version | 2.22.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As aws-sdk is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
See changelog for more information.
The new version differs by 8 commits .
cd6f728
Updates SDK to v2.23.0
440ed1e
Merge pull request #1382 from johanneswuerbach/fix-buf-size-eq-part-size
b982ac8
Fix ManagedUpload never finishes when stream size == part size
3fc5ce6
Merge pull request #1384 from jeskew/docs/delete-dev-guide
f3c444e
Remove unused developer guide
7589985
Fixes yardoc generation when service models use mixed-casing (#1383)
6db3ffa
Merge pull request #1377 from jeskew/docs/generate-service-list-to-separate-file
d8f1b60
Generate the list of services supported by the SDK to a separate file.
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
3.0.2
to 3.0.3
.This version is covered by your current version range and after updating it in your project the build failed.
coveralls is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
As suggested by NPM and Snyk.
The new version differs by 1 commits.
aa2519c
dependency security audit fixes from npm & snyk (#210)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | aws-sdk |
Current Version | 2.16.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As aws-sdk is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
See changelog for more information.
The new version differs by 4 commits .
6a1b00c
Updates SDK to v2.17.0
8e15313
Allow the service configuration credentials to be nulled (#1367)
2ebc99b
Merge pull request #1355 from ehartford/master
6fca13a
add AWSError to exports
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
We are planning to release Flydrive version 1.0 soon. This will be a relatively huge release that include a number of necessary breaking changes.
The code of the release is currently in the next
branch.
list(location: string)
copyToDisk(location: string, dest: string, destDisk: Storage)
moveToDisk(location: string, dest: string, destDisk: Storage)
getTimestamp(location: string)
The FTP driver has been removed and will probably not be added again. Feel free to create you own driver and extend the manager with it.
Proxies have been removed, that means we doesn't support magic method forwarding anymore. You will need to build an abstraction around it (like it's done in the Adonis implementation) if you want to keep this feature.
// Before
storage.exists(...)
// Now
storage.disk().exists(...)
storage.disk() // Returns the default disk (specified in the config)
storage.disk('awsCloud') // Returns the driver for the disk "awsCloud"
storage.disk('awsCloud', customConfig) // Overwrite the default configuration of the disk
Since all drivers will have a consistent returns you will need to adapt your code to the new interface/abstraction we will create.
A good example is the put
method that currently only return a boolean
to give you insight if the file as been written or not.
However, some drivers like S3
return many information about the new file (#52). To avoid loosing those information we will create a common response object for those methods that will have always the same properties across all drivers.
If we don't handle a specific use case you will still be able to access the real response by using the raw
property.
I personally have use for a list()
method, specifically for S3 buckets. I've written this in other projects but I would like to make a PR for this feature on the S3 driver.
Is this something you think would be accepted? I could write the equivalent for the filesystem driver too, but I would use something like the klaw package. Thoughts?
this lib is great but still missing few of features such as remove folder, get files list inside a folder compress folder inside a [zip|tar|gz|7z|...]
good luck with your job and activities @RomainLanz
6.0.0
to 6.1.0
.This version is covered by your current version range and after updating it in your project the build failed.
dotenv is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 7 commits.
78546c1
6.1.0
d7605ae
update changelog for 6.1.0
3e3efc8
add debug option (#339)
0fe6114
Added link to env-path (#335)
47943e4
upgrade dependencies (#338)
178e4ba
Improve CLI option regex (#325)
85ece25
Add 6.0.0 to changelog (#316)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
how can i do that?
const params = { acl: 'public-read' }
body.avatar = await Drive.getSignedUrl(`${body.username}.${file.subtype}`, params)
NOT WORKING
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing 🚨 |
---|---|
Dependency | aws-sdk |
Current Version | 2.215.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
aws-sdk is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
See changelog for more information.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
5.12.0
to 5.12.1
.This version is covered by your current version range and after updating it in your project the build failed.
eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
eb5c401
Chore: use meta.messages in some rules (2/4) (refs #9870) (#10773) (薛定谔的猫)aa56247
Fix: avoid loading core rules dynamically from FS in Linter (#11278) (Peter Metz)04450bb
Docs: clarify process for adding committers (#11272) (Kai Cataldo)3ffcf26
Docs: add @g-plane as committer (#11277) (Kai Cataldo)c403445
Fix: warn constant on RHS of || in no-constant-condition (fixes #11181) (#11253) (Merlin Mason)9194f45
Fix: Manage severity of 1 with TAP reporter (fixes #11110) (#11221) (Gabriel Cousin)000f495
Docs: fix example for sort-imports ignoreDeclarationSort (#11242) (Remco Haszing)7c0bf2c
Docs: Add npx
usage to Getting Started guide (#11249) (eyal0803)da9174e
Docs: fixes typo peerDepencies (#11252) (Christian Kühl)9c31625
Docs: Improve custom formatter docs (#11258) (Nicholas C. Zakas)The new version differs by 12 commits.
faf3c4e
5.12.1
1010c98
Build: changelog update for 5.12.1
eb5c401
Chore: use meta.messages in some rules (2/4) (refs #9870) (#10773)
aa56247
Fix: avoid loading core rules dynamically from FS in Linter (#11278)
04450bb
Docs: clarify process for adding committers (#11272)
3ffcf26
Docs: add @g-plane as committer (#11277)
c403445
Fix: warn constant on RHS of || in no-constant-condition (fixes #11181) (#11253)
9194f45
Fix: Manage severity of 1 with TAP reporter (fixes #11110) (#11221)
000f495
Docs: fix example for sort-imports ignoreDeclarationSort (#11242)
7c0bf2c
Docs: Add npx
usage to Getting Started guide (#11249)
da9174e
Docs: fixes typo peerDepencies (#11252)
9c31625
Docs: Improve custom formatter docs (#11258)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
I am not sure why AWS driver takes only 3 config options in constructor.
accessKeyId: config.key,
secretAccessKey: config.secret,
region: config.region
AWS s3 sdk takes a lot of other configuration options and this driver is limiting features provided by AWS.
I was looking at using local s3 server provided by Atlassian localstack with Adonis Framework. But I could not specify s3 endpoint with the driver. It would be same issue if someone wanted to set proxy config. I think the driver should take all s3 Parameters in config and not just 3. Better option would to allow injecting s3 Object to the driver so anyone could create their s3 object with their custom configuration and pass it to driver.
5.5.1
to 5.6.0
.This version is covered by your current version range and after updating it in your project the build failed.
semver is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
2.14.0
to 2.15.0
.This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 34 commits.
767f01a
bump to v2.15.0
038d668
bump webpack resolver to v0.11.0
20a8f3b
bump utils to v2.3.0
1e4100d
changelog note for #1261
548ea02
added support for argv parameter of webpack`s config-as-a-function (#1261)
fcf2ce7
Merge pull request #1254 from ljharb/travis
64d9be7
allow_failures for dicey Node/ESLint intersection
73080d0
dep-time-travel: use older versions of dependencies
05c3935
repair no-deprecated
for ESLint* 5
10c9811
node 4 fix for test util
f165237
ah geez, bumping babel-eslint breaks no-amd/no-cjs
acfb6e9
jk, test against eslint 2/3 but skip Typescript tests.
b686f9d
drop ESLint 2/3 from Travis/Appveyor
cf1f6f4
[Deps] update debug
, eslint-import-resolver-node
, has
, lodash
, minimatch
, resolve
d290a87
[Dev Deps] update babylon
, coveralls
, eslint-import-resolver-typescript
, gulp
, linklocal
, nyc
, redux
, rimraf
, sinon
, typescript-eslint-parser
There are 34 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Hey, I would love to have support for Google cloud storage. The Google team recently published a library https://www.npmjs.com/package/@google-cloud/storage and it would be great to have this integrated as an alternative to AWS S3.
Branch | Build failing 🚨 |
---|---|
Dependency | aws-sdk |
Current Version | 2.225.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
aws-sdk is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
See changelog for more information.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
On a clean fork the following tests fail.
Yes, .env file has SES_KEY, SES_SECRET, SES_BUCKET & SES_REGION have values 😃
Removing lines 211-213 from AwsS3.js slightly remedies the issue...
https://github.com/Slynova-Org/node-flydrive/blob/112ec6385199a3ef78f0c522ed3520dc4d980d9b/src/Drivers/AwsS3.js#L207-L216
It seems as though, at least in my case, this
https://github.com/Slynova-Org/node-flydrive/blob/112ec6385199a3ef78f0c522ed3520dc4d980d9b/src/Drivers/AwsS3.js#L211 will always be truthy.
Branch | Build failing 🚨 |
---|---|
Dependency | aws-sdk |
Current Version | 2.20.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As aws-sdk is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
See changelog for more information.
The new version differs by 3 commits .
bc5aab6
Updates SDK to v2.21.0
e43c127
Adds support for Organizations
ffff0d0
Adds service MechanicalTurkRequester
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | aws-sdk |
Current Version | 2.311.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
aws-sdk is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
See changelog for more information.
The new version differs by 6 commits.
4ed5104
Updates SDK to v2.312.0
3839328
Create no-response.yml
59f1eb0
remove stalebot
23701ac
enable stale bot
f5a3482
update typings for credentialsProviderChain & httpOptions (#2240)
167bc31
retry request for Batch TooManyRequestsException (#2246)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing 🚨 |
---|---|
Dependency | @slynova/eslint-config |
Current Version | 1.0.4 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@slynova/eslint-config is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing 🚨 |
---|---|
Dependency | eslint-plugin-import |
Current Version | 2.9.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 34 commits.
47ac30f
bump webpack resolver to v0.9.0
6356a78
bump to v2.10.0
82f67e6
bump utils to v2.2.0
ed719a3
Merge branch 'no-cycles'
ab44320
changelog notes
b34d9ff
Add autofixer for order rule (#908)
e215b61
try solution from appveyor/ci#650
231874c
update eslint-import-resolver-webpack homepage to the source of the package (#997)
ad66aea
smh.
d81f48a
no-cycle: maxDepth tests + docs
6933fa4
no-cycle: initial docs + maxDepth option
864dbcf
no-cycle: explicit CJS/AMD tests
314c0b7
fix issue (and add conspicuously absent test) with 'export *'
f7c48b5
no-cycle: real rule! first draft, perf is likely atrocious
0c21c4e
sublime-linter project tweaks
There are 34 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Promise constructor anti-pattern can be noticed in these lines (more info):
https://github.com/Slynova-Org/node-flydrive/blob/7577b1bccce3dd6b8ee39faeda29c55e6ac8f6b6/src/Drivers/FTP.js#L97
https://github.com/Slynova-Org/node-flydrive/blob/7577b1bccce3dd6b8ee39faeda29c55e6ac8f6b6/src/Drivers/FTP.js#L141
Also, some tests are failing with different ftp servers (the one commented in the docker-compose
file at #54 ). I can't really debug the issue, but looks like some exceptions are not being handled. Like connection errors, closed connections and finalized connections. I think the driver should have a policy for that kind of events, and throw a proper exception. But I don't have that much idea about FTP sadly. (who consumes FTP servers in node apps anyway? 🤣 )
FTP Driver
1. move file
(node:32) UnhandledPromiseRejectionWarning: Error: 550 Rename/move failure
at Ftp.parse (/home/node/app/node_modules/jsftp/lib/jsftp.js:223:11)
at Ftp.parseResponse (/home/node/app/node_modules/jsftp/lib/jsftp.js:146:8)
at Stream.pipeline.on.data (/home/node/app/node_modules/jsftp/lib/jsftp.js:112:10)
at emitOne (events.js:116:13)
at Stream.emit (events.js:211:7)
at ResponseParser.reemit (/home/node/app/node_modules/duplexer/index.js:70:25)
at emitOne (events.js:116:13)
at ResponseParser.emit (events.js:211:7)
at readableAddChunk (/home/node/app/node_modules/readable-stream/lib/_stream_readable.js:195:16)
at ResponseParser.Readable.push (/home/node/app/node_modules/readable-stream/lib/_stream_readable.js:162:10)
(node:32) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:32) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
As far as I know, the server is returning a 550 Rename/move failure
for move file
test case of the FTP Driver, and looks like it isn't properly handling the error.
This may have something to do with how promises are being handled:
https://stackoverflow.com/questions/33445415/javascript-promises-reject-vs-throw
https://stackoverflow.com/questions/43036229/is-it-an-anti-pattern-to-use-async-await-inside-of-a-new-promise-constructor
You can test it by cloning my fork, and running the tests as described in #54
With ftp driver I can only use put method for the file without any parent folder:
Any solution for this?
Appreciate your help
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.