thisconnect / fildes Goto Github PK

View Code? Open in Web Editor NEW

8.0 8.0 1.0 692 KB

Magicless helps working with file descriptors

License: MIT License

JavaScript 100.00%

filesystem fs promise

fildes's People

Contributors

Stargazers

Watchers

Forkers

eerne

fildes's Issues

fs.link (mkdirp) Error: EEXIST: file already exists or ENOENT: no such file or directory

If fs.link fails for the first time it tries to mkdirp. If the path is on a file different Errors are thrown

On OS X: Error: ENOTDIR: not a directory, mkdir
On Windows: Error: EEXIST: file already exists, mkdir

  link dest error

    √ Error: EEXIST: file already exists, mkdir
    √ is Error

    × error.code is ENOTDIR
    ------------------------
      operator: equal
      expected: 'ENOTDIR'
      actual:   'EEXIST'

    √ error.syscal is mkdir

An in-range update of codecov is breaking the build 🚨

The devDependency codecov was updated from `3.2.0` to `3.3.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

codecov 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.

Status Details

✅ ci/circleci: node-10: Your tests passed on CircleCI! (Details).
✅ ci/circleci: node-8: Your tests passed on CircleCI! (Details).
✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
❌ codecov/project: 91.44% (-3.22%) compared to 64909c9 (Details).
✅ codecov/patch: Coverage not affected when comparing 64909c9...7a487eb (Details).

Release Notes for v3.3.0

Added pipe --pipe, -l

Commits

The new version differs by 21 commits.

d81c4f4 Merge pull request #111 from TomSputz/pipe
aa5a2b0 feat(services): add Cirrus CI (#117)
00d484b v3.2.0
ad51194 Satisfy ESLint configuration
5f2d0e6 Fixed path to npm bin folder
afcf3e5 Fixed merge conflicts
145cb46 updated PR with changes from upstream
2b2ad02 merge package-lock.json from upstream
bf0c751 added documentation
9445f72 fixed wrong fixture file names
348cf7b lock dependencies
fbf17d2 remove timer because slow CI servers need more than half a second before data is flowing - switch to use --pipe or -l as signal to codecov to recieve data via stdin
b145b19 Merge branch 'master' into pipe
d460065 check if the stale state was due to using the data event instead of the readable event
e8ca9ed be very explicit about exiting process and clearing timeout

There are 21 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

move everything with a dependency to fildes-extra

An in-range update of nyc is breaking the build 🚨

The devDependency nyc was updated from `14.0.0` to `14.1.0`.

🚨 View failing branch.

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.

Status Details

✅ ci/circleci: node-10: Your tests passed on CircleCI! (Details).
✅ ci/circleci: node-8: Your tests passed on CircleCI! (Details).
✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
❌ codecov/project: 91.44% (-3.32%) compared to 3222d07 (Details).
✅ codecov/patch: Coverage not affected when comparing 3222d07...3a6da2f (Details).

Commits

The new version differs by 15 commits.

c5d90fa chore(release): 14.1.0
5cc05f4 chore: Update dependencies
1e39ae1 chore: Refresh snapshots, update test/config-override.js to use helpers (#1085)
3d9eaa4 fix: Purge source-map cache before reporting if cache is disabled. (#1080)
132a074 feat: Add support for env.NYC_CONFIG_OVERRIDE (#1077)
6fc109f chore: node.js 12 compatibility for object snapshot test. (#1084)
a7bc7ae fix: Use correct config property for parser plugins (#1082)
600c867 chore: Convert some tap tests to run parallel and use snapshots. (#1075)
56591fa docs: instrument docs update [skip ci] (#1063)
ca84c42 docs(codecov): favour npx over installing locally [skip ci] (#1074)
85c1eac chore: Add test for nyc --no-clean. (#1071)
21fb2c8 fix: Exit with code 1 when nyc doesn't know what to do. (#1070)
0f745ca chore: Use class to declare NYC (#1069)
ca37ffa feat: add support for yaml configuration file (#1054)
c4fcf5e fix: Do not crash when nyc is run inside itself. (#1068)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

fildes.open should mkdir depending on flag

Regarding https://nodejs.org/api/fs.html#fs_fs_open_path_flags_mode_callback

fildes.open should mkdir when flag is 'w', 'w+', 'a' and 'a+'

in this case

catch error
if Error: ENOENT: no such file or directory try mkdir
then try opening again

fs.access EACCES actual Error: EPERM: operation not permitted

Expected EPERM instead of EACCES, for fs.access
Test fail on Window 10 with Node.js 5.3.0

 stats

   √ Error: EPERM: operation not permitted, access

   × error.code is EACCES
   -----------------------
     operator: equal
     expected: 'EACCES'
     actual:   'EPERM'

   √ should be equal

   × should not pass
   ------------------
     operator: fail


   × .end() called twice
   ----------------------
     operator: fail

An in-range update of prettier is breaking the build 🚨

The devDependency prettier was updated from `1.14.2` to `1.14.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier 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.

Status Details

✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 1.14.3

🔗 Changelog

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

nodegit 0.5.0 on travis fails

https://travis-ci.org/thisconnect/nodegit-kit/builds/89676720

> [email protected] test /home/travis/build/thisconnect/nodegit-kit
> tape ./test/test.js | tap-spec
/home/travis/build/thisconnect/nodegit-kit/node_modules/nodegit/lib/nodegit.js:13
    throw ex;
    ^
Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' not found (required by /home/travis/build/thisconnect/nodegit-kit/node_modules/nodegit/build/Release/nodegit.node)
    at Error (native)
    at Object.Module._extensions..node (module.js:460:18)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (/home/travis/build/thisconnect/nodegit-kit/node_modules/nodegit/lib/nodegit.js:8:12)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
  ✖ No tests found
npm ERR! Test failed.  See above for more details.
The command "npm test" exited with 1.
Done. Your build exited with 1.

add tests for passing fd to fs.file* only Node 5.x

nodejs/node#3163

An in-range update of nyc is breaking the build 🚨

Version 11.2.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	11.1.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc 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 💪

Status Details

✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 18 failing files. Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 7 commits.

b2ff72d chore(release): 11.2.0
97b962e chore: explicit update of istanbul-lib-instrument (#662)
0dcceda feat: allow cwd to be configured see #620
0fc6d8f chore: add support for --cwd (#542) (#620)
658dba4 fix: remove excluded files from coverage before writing (#649)
dd40dc5 feat: add possibility to filter coverage-maps (#637)
fb3ab92 docs: add link to community slack (#639)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

add trash and empty-trash

https://github.com/sindresorhus/trash
https://github.com/sindresorhus/empty-trash

An in-range update of eslint is breaking the build 🚨

Version 4.6.0 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	4.5.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint 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 💪

Status Details

❌ bitHound - Code 18 failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v4.6.0

56dd769 Docs: fix link format in prefer-arrow-callback.md (#9198) (Vse Mozhet Byt)
6becf91 Update: add eslint version to error output. (fixes #9037) (#9071) (薛定谔的猫)
0e09973 New: function-paren-newline rule (fixes #6074) (#8102) (Teddy Katz)
88a64cc Chore: Make parseJsonConfig() a pure function in Linter (#9186) (Teddy Katz)
1bbac51 Fix: avoid breaking eslint-plugin-eslint-comments (fixes #9193) (#9196) (Teddy Katz)
3e8b70a Fix: off-by-one error in eslint-disable comment checking (#9195) (Teddy Katz)
73815f6 Docs: rewrite prefer-arrow-callback documentation (fixes #8950) (#9077) (Charles E. Morgan)
0d3a854 Chore: avoid mutating report descriptors in report-translator (#9189) (Teddy Katz)
2db356b Update: no-unused-vars Improve message to include the allowed patterns (#9176) (Eli White)
8fbaf0a Update: Add configurability to generator-star-spacing (#8985) (Ethan Rutherford)
8ed779c Chore: remove currentScopes property from Linter instances (refs #9161) (#9187) (Teddy Katz)
af4ad60 Fix: Handle error when running init without npm (#9169) (Gabriel Aumala)
4b94c6c Chore: make parse() a pure function in Linter (refs #9161) (#9183) (Teddy Katz)
1be5634 Chore: don't make Linter a subclass of EventEmitter (refs #9161) (#9177) (Teddy Katz)
e95af9b Chore: don't include internal test helpers in npm package (#9160) (Teddy Katz)
6fb32e1 Chore: avoid using private Linter APIs in astUtils tests (refs #9161) (#9173) (Teddy Katz)
de6dccd Docs: add documentation for Linter methods (refs #6525) (#9151) (Teddy Katz)
2d90030 Chore: remove unused assignment. (#9182) (薛定谔的猫)
d672aef Chore: refactor reporting logic (refs #9161) (#9168) (Teddy Katz)
5ab0434 Fix: indent crash on sparse arrays with "off" option (fixes #9157) (#9166) (Teddy Katz)
c147b97 Chore: Make SourceCodeFixer accept text instead of a SourceCode instance (#9178) (Teddy Katz)
f127423 Chore: avoid using private Linter APIs in Linter tests (refs #9161) (#9175) (Teddy Katz)
2334335 Chore: avoid using private Linter APIs in SourceCode tests (refs #9161) (#9174) (Teddy Katz)
2dc243a Chore: avoid using internal Linter APIs in RuleTester (refs #9161) (#9172) (Teddy Katz)
d6e436f Fix: no-extra-parens reported some parenthesized IIFEs (fixes #9140) (#9158) (Teddy Katz)
e6b115c Build: Add an edit link to the rule docs’ metadata (#9049) (Jed Fox)
fcb7bb4 Chore: avoid unnecessarily complex forEach calls in no-extra-parens (#9159) (Teddy Katz)
ffa021e Docs: quotes rule - when does \n require backticks (#9135) (avimar)
60c5148 Chore: improve coverage in lib/*.js (#9130) (Teddy Katz)

Commits

The new version differs by 31 commits.

8f01a99 4.6.0
c0acbf2 Build: changelog update for 4.6.0
56dd769 Docs: fix link format in prefer-arrow-callback.md (#9198)
6becf91 Update: add eslint version to error output. (fixes #9037) (#9071)
0e09973 New: function-paren-newline rule (fixes #6074) (#8102)
88a64cc Chore: Make parseJsonConfig() a pure function in Linter (#9186)
1bbac51 Fix: avoid breaking eslint-plugin-eslint-comments (fixes #9193) (#9196)
3e8b70a Fix: off-by-one error in eslint-disable comment checking (#9195)
73815f6 Docs: rewrite prefer-arrow-callback documentation (fixes #8950) (#9077)
0d3a854 Chore: avoid mutating report descriptors in report-translator (#9189)
2db356b Update: no-unused-vars Improve message to include the allowed patterns (#9176)
8fbaf0a Update: Add configurability to generator-star-spacing (#8985)
8ed779c Chore: remove currentScopes property from Linter instances (refs #9161) (#9187)
af4ad60 Fix: Handle error when running init without npm (#9169)
4b94c6c Chore: make parse() a pure function in Linter (refs #9161) (#9183)

There are 31 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of make-dir is breaking the build 🚨

Version 1.3.0 of make-dir was just published.

Branch	Build failing 🚨
Dependency	`make-dir`
Current Version	1.2.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

make-dir 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.

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ bitHound - Code No failing files. Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 2 commits.

e962394 1.3.0
0f58aa0 Node.js 10 compatibility

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Error: ENAMETOOLONG

Error: ENAMETOOLONG: name too long, mkdir /Users/admin/source/xggd-gaailio/daua/kelksm3kjncsoidncoier/resources/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/youland/coroga/goliuiithin-emgoeru-miu-uieco-yu-axuauuaing/suory/21699130

An in-range update of codecov is breaking the build 🚨

Version 2.3.1 of codecov was just published.

Branch	Build failing 🚨
Dependency	codecov
Current Version	2.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ bitHound - Code 18 failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details

Commits

The new version differs by 3 commits.

4e5854e v2.3.1
ce3d271 rollback request to v2.77.0 (#73)
c1d1ace Adding node v8 (#71)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of prettier is breaking the build 🚨

Version 1.8.2 of prettier was just published.

Branch	Build failing 🚨
Dependency	prettier
Current Version	1.8.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ bitHound - Code No failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of codecov is breaking the build 🚨

The devDependency codecov was updated from `3.1.0` to `3.2.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ ci/circleci: node-8: Your tests passed on CircleCI! (Details).
✅ ci/circleci: node-10: Your tests passed on CircleCI! (Details).
✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 3 commits.

e427d90 feat(services): add azure pipelines (#114)
023d204 Use small HTTP dependency (#110)
500f308 Update Readme

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

fs.write create a new directory (Error: ENOENT: no such file or directory, open)

fs.write / fildes.write with 'w' flag does not create a new directory.

Error: ENOENT: no such file or directory, open

An in-range update of eslint-plugin-prettier is breaking the build 🚨

Version 2.3.0 of eslint-plugin-prettier just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-prettier
Current Version	2.2.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-prettier 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 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ bitHound - Code Error analyzing branch. Details
❌ bitHound - Dependencies Error analyzing branch. Details

Commits

The new version differs by 6 commits.

cdd1a83 Build: update package.json and changelog for v2.3.0
bc89153 Update: Support .prettierrc config files (fixes #46) (#55)
95f0808 Docs: .eslintrc.json > .eslintrc (#52)
c777111 Upgrade: jest-docblock to ^21.0.0 (#50)
56deffa Chore: upgrade prettier to ^1.6.1 (#49)
5ea0526 Chore: use eslint-plugin-self for linting (#47)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

fildes.rm

An in-range update of eslint-plugin-promise is breaking the build 🚨

Version 3.6.0 of eslint-plugin-promise was just published.

Branch	Build failing 🚨
Dependency	eslint-plugin-promise
Current Version	3.5.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-promise 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.

Status Details

❌ bitHound - Code 18 failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of prettier-eslint-cli is breaking the build 🚨

Version 4.2.2 of prettier-eslint-cli just got published.

Branch	Build failing 🚨
Dependency	prettier-eslint-cli
Current Version	4.2.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As prettier-eslint-cli 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 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
✅ bitHound - Dependencies No failing dependencies. Details
❌ bitHound - Code 18 failing files. Details

Release Notes

v4.2.2

4.2.2 (2017-08-30)

Bug Fixes

Bumped eslint, prettier-eslint to latest with updates (#97) (02386871, closes #94)

Commits

The new version differs by 1 commits.

0238687 fix: Bumped eslint, prettier-eslint to latest with updates (#97)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

fs.writeFile Error: EISDIR: illegal operation on a directory, open

Test EISDIR: illegal operation on a directory, open for writeFile when writing a file on a directory.

var file = require('fildes');

file.writeFile('./this/is/a/directory', 'should thorw an EISDIR Error')
.catch(function(error){
    console.error(error);
});

fs.read without passing buffer

Allow calling fildes read without a buffer.

file.read(path, {
  'offset': 0,
  'length': 3
})

An in-range update of eslint is breaking the build 🚨

Version 4.1.1 of eslint just got published.

Branch	Build failing 🚨
Dependency	eslint
Current Version	4.1.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint 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 💪

Status Details

✅ bitHound - Code No failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v4.1.1

f307aa0 Fix: ensure configs from a plugin are cached separately (fixes #8792) (#8798) (Teddy Katz)
8b48ae8 Docs: Add doc on parser services (fixes #8390) (#8795) (Victor Hom)
0d041e7 Fix: avoid crashing when using baseConfig with extends (fixes #8791) (#8797) (Teddy Katz)
03213bb Chore: improve comment explanation of indent internal functions (#8800) (Teddy Katz)
d2e88ed Chore: Fix misleading comment in ConfigCache.js (#8799) (Teddy Katz)

Commits

The new version differs by 7 commits.

1df6a01 4.1.1
79a4482 Build: changelog update for 4.1.1
f307aa0 Fix: ensure configs from a plugin are cached separately (fixes #8792) (#8798)
8b48ae8 Docs: Add doc on parser services (fixes #8390) (#8795)
0d041e7 Fix: avoid crashing when using baseConfig with extends (fixes #8791) (#8797)
03213bb Chore: improve comment explanation of indent internal functions (#8800)
d2e88ed Chore: Fix misleading comment in ConfigCache.js (#8799)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

fs.write at position fails with 'w' or 'w+' overwrites content with \x00

fildes/test/test-write.js

Line 24 in eb9f553

tape('write buffer at position', function(t){

write buffer at position

✔ file written

✖ should be equal
------------------
  operator: equal
  expected: 'foo bar bOz'
  actual:   '\x00\x00\x00\x00\x00\x00\x00\x00bOz'

Promises for all async fs methods that use fd

fs.ftruncate, fs.fchown, fs.fchmod, fs.futimes, fs.fsync

An in-range update of prettier is breaking the build 🚨

Version 1.10.1 of prettier was just published.

Branch	Build failing 🚨
Dependency	prettier
Current Version	1.10.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ bitHound - Dependencies No failing dependencies. Details
✅ bitHound - Code No failing files. Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of prettier is breaking the build 🚨

Version 1.13.2 of prettier was just published.

Branch	Build failing 🚨
Dependency	`prettier`
Current Version	1.13.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ bitHound - Dependencies No failing dependencies. Details
✅ bitHound - Code No failing files. Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of prettier is breaking the build 🚨

Version 1.6.0 of prettier just got published.

Branch	Build failing 🚨
Dependency	prettier
Current Version	1.5.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As prettier 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 💪

Status Details

❌ bitHound - Dependencies null Details
❌ bitHound - Code null Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

1.6.0: Config File, JSX

I want to give a special shout out to @azz who has been maintaining the repository and implementing a bunch of the changes in this release as I had less time to devote to prettier due to vacation and switching team :)

Highlights

Configuration

Implement cosmiconfig for workspace configuration (#2434) by @azz

Since the very first release of prettier, people have asked for a .prettierrc file. We've been trying to have as few options as possible and tried to avoid being one more .dotfile that you have to have when starting a new project.

But, the truth is, we need to have some way to configure prettier that can be kept in sync with all the integrations. By not having one, we pushed the problem to them and saw a bunch of incompatible ways of handling the problem. So now, it's handled by prettier itself.

// .prettierrc
{
  "trailingComma": "es5",
  "singleQuote": true
}

For more information on configuration file support, see the README.

Support .prettierignore files (#2412) by @evilebottnawi

Along with telling what configuration to use, you can write a file .prettierignore to tell which files not to convert.

# .prettierignore
dist/
package.json

JSX

Improve JSX Formatting (#2398) by @suchipi

The last big friction point from people trying to adopt prettier was around how JSX was being printed. We went through all the issues that were raised and made a bunch of changes:

Arrow Function Expressions returning JSX will now add parens when the JSX breaks

// Before
const Component = props =>
  <div>
    Hello {props.name}!
  </div>;
// After

const Component = props => (

<div>

Hello {props.name}!

</div>

);

Conditional expressions within (or containing) JSX are formatted in a different way using parenthesis

// Before
<div>
  {props.isVisible
    ? <BaseForm
        url="/auth/google"
        method="GET"
      />
    : <Placeholder />}
</div>;
// After

<div>

{props.isVisible ? (

<BaseForm

url="/auth/google"

method="GET"

/>

) : (

<Placeholder />

)}

</div>

JSX in logical expressions (|| or &&) is always wrapped in parens when the JSX breaks

// Before
<div>
  {props.isVisible &&
    <BaseForm
      url="/auth/google"
      method="GET"
    />}
</div>;
// After

<div>

{props.isVisible && (

<BaseForm

url="/auth/google"

method="GET"

/>

)}

</div>

Hopefully this is going to be more in line with how the majority of the community is writing JSX and we can have prettier be used in more place ;)

Inline single expressions in JSX (#2442) by @karl

With JSX, we started by respecting a lot of line breaks that were in the original source. This had the advantage of doing fewer changes to your codebase but chipped away the value of a consistent pretty printer as the same semantic code could be written in two ways.

During each new release we've tightened this and made decisions around how to always print a piece of code. The latest of those is what happens if there's a single child in a JSX object, we're now always going to inline it.

// Before
return (
  <div>
    {this.props.test}
  </div>
);
return <div>{this.props.test}</div>;
// After

return <div>{this.props.test}</div>;

return <div>{this.props.test}</div>;

Ensure there is a line break after leading JSX white space (#2348) by @karl

Leading JSX empty spaces are now on their own line. It looked weird to have them before a tag as it "indented" it differently compared to the rest.

// Before
<span className="d1">
  {' '}<a
    href="https://github.schibsted.io/finn/troika"
    className="link"
  />
</span>
// After

<span className="d1">

{' '}

<a

href="https://github.schibsted.io/finn/troika"

className="link"

/>

</span>

Other Changes

JSON

Use babylon.parseExpression for JSON (#2476) by @josephfrazier

We used to use a strict JSON parser that would throw if there was a comment or a trailing comma. This was inconvenient as many JSON files in practice are parsed using JavaScript or json5 that are not as strict. Now, we have relaxed this and are using the JavaScript parser to parse and print JSON. This means that comments will be maintained if there were some.

Note that this is purely additive, if your original file was JSON compliant, it will keep printing a valid JSON.

// Before
Syntax error
// After

{ / some comment / "a": 1 }

JavaScript

Add more supervisory parens (#2423) by @azz

Parenthesis are a hot topic because they are not part of the AST, so prettier ignores all the ones you are putting and re-creating them from scratch. We went through all the things that people reported and came up with a few edge cases that were very confusing when comparisons were chained and % was mixed with * or /.

One thing that we are not changing is the fact that we remove extra parenthesis around combinations of basic arithmetic operators: +-*/.

// Before
x !== y === z;
x * y % z;
// After

(x !== y) === z;

(x * y) % z;

Implement prettier-ignore inside JSX (#2487) by @azz

It's useful to be able to ignore pieces of JSX, it's now possible to add a comment inside of a JSX expression to ignore the formatting of the next element.

// Before
<Component>
  {/*prettier-ignore*/}
  <span ugly format="" />
</Component>
// Before

<Component>

{/prettier-ignore/}

<span     ugly  format=''   />

</Component>

Do not swallow prettier-ignore comments (#2664)

In order to support some edge cases, in the internals, we have the ability to avoid printing comments in a generic way and print them in the call site instead. It turns out that when we used prettier-ignore, we didn't print the comments at all! This is now fixed.

// Before
push(
  <td> :)
  </td>,
);
// After

push(

// prettier-ignore

<td> :)

</td>,

);

Fix indentation of a do-while condition (#2359) by @jsnajdr

It took 6 months for someone to report that do-while were broken when the while condition is multi-line, it confirms my hunch that this construct is not widely used in practice.

// Before
do {} while (
  someVeryLongFunc(
  someVeryLongArgA,
  someVeryLongArgB,
  someVeryLongArgC
)
);
// After

do {} while (

someVeryLongFunc(

someVeryLongArgA,

someVeryLongArgB,

someVeryLongArgC

)

);

Break sequence expressions (#2388) by @bakkot

Another underused feature of JavaScript is sequence expressions. We used to do a bad job at printing them when they would go multi-line, this has been corrected :)

// Before
(a = b ? c : "lllllllllllllllllllllll"), (a = b
  ? c
  : "lllllllllllllllllllllll"), (a = b ? c : "lllllllllllllllllllllll"), (a = b
  ? c
  : "lllllllllllllllllllllll"), (a = b ? c : "lllllllllllllllllllllll");
// After

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll'),

(a = b ? c : 'lllllllllllllllllllllll')

Trim trailing whitespace from comments (#2494) by @azz

We took the stance with prettier to remove all the trailing whitespaces. We used to not touch comments because it's user generated, but that doesn't mean that they should have whitespace :)

// Before // There is some space here ->______________

// After
// There is some space here ->

Fix interleaved comments in class decorators (#2660, #2661)

Our handling for comments inside of the class declaration was very naive, we would just move all the comments to the top. We now are more precise and respect the comments that are interleaved inside of decorators and around extends.

// Before
// A
// B
// C
@Foo()
@Bar()
class Bar {}
// After

// A

@Foo()

// B

@Bar()

// C

class Bar {}

Improve bind expression formatting (#2493) by @azz

Bind expressions are being discussed at TC39 and we figured we could print it with prettier. We used to be very naive about it and just chain it. Now, we use the same logic as we have for method chaining with the . operator for it. We also fixed some edge cases where it would output invalid code.

// Before
observable::filter(data => data.someTest)::throttle(() =>
  interval(10)::take(1)::takeUntil(observable::filter(data => someOtherTest))
)::map(someFunction);
// After

observable

::filter(data => data.someTest)

::throttle(() =>

interval(10)::take(1)::takeUntil(observable::filter(data => someOtherTest))

)

::map(someFunction);

Add support for printing optional catch binding (#2570) by @existentialism

It's being discussed at TC39 to be able to make the argument of a catch(e) optional. Let's make sure we can support it in prettier if people use it.

// Before
Syntax error
// After

try {} catch {}

Add support for printing optional chaining syntax (#2572) by @azz

Another new proposal being discussed at TC39 is an optional chaining syntax. This is currently a stage 1 proposal, so the syntax may change at any time.

obj?.prop       // optional static property access
obj?.[expr]     // optional dynamic property access
func?.(...args) // optional function or method call

Handle Closure Compiler type cast syntax correctly (#2484) by @yangsu

Comments are tricky to get right, but especially when they have meaning based on where they are positioned. We're now special casing the way we deal with comments used as type cast for Closure Compiler such that they keep having the same semantics.

// Before
let assignment /** @type {string} */ = getValue();
// After

let assignment = /** @type {string} */ (getValue());

Inline first computed property lookup in member chain (#2670) by @azz

It looks kind of odd to have a computed property lookup on the next line, so we added a special case to inline it.

// Before
data
  [key]('foo')
  .then(() => console.log('bar'))
  .catch(() => console.log('baz'));
// After

data[key]('foo')

.then(() => console.log('bar'))

.catch(() => console.log('baz'));

Flow

Support opaque types and export star (#2543, #2542) by @existentialism

The flow team introduced two very exciting features under a new syntax. We now support them in prettier. I've personally been waiting for opaque types for a veerrryyyy long time!

// Before
Syntax error
// After

opaque type ID = string;

export type * from "module";

Strip away unnecessary quotes in keys in type objects and interfaces (#2643)

We've been doing this on JavaScript objects since the early days of prettier but forgot to apply the same thing to Flow and TypeScript types.

// Before
type A = {
  "string": "A";
}
// After

type A = {

string: "A";

}

Print TypeParameter even when unary function type (#2406) by @danwang

Oopsy, we were dropping the generic in this very specific case.

// Before
type myFunction = A => B;
// After

type myFunction = <T>(A) => B;

Keep parens around FunctionTypeAnnotation inside ArrayTypeAnnotation (#2561) by @azz

Parenthesis... someday we'll get all of them fixed :)

// Before
const actionArray: () => void[] = [];
// After

const actionArray: (() => void)[] = [];

TypeScript

Support TypeScript 2.5 RC (#2672) by @azz

TypeScript 2.5 RC was recently announced, allowing you to use the upcoming "optional catch binding" syntax in TypeScript, too. 🎉

Don't add namespace keyword to global declaration (#2329) by @azz

// Before
namespace global {
  export namespace JSX {  }
}
// After

global {

export namespace JSX {}

}

Fix <this.Component /> (#2472) by @backus

Thanks to the untyped and permissive nature of JavaScript, we've been able to concat undefined to a string and get some interesting code as a result. Now fixed for this case :)

// Before
<undefined.Author />
// After

<this.Author />

Allow type assertions to hug (#2439) by @azz

We want to make sure that all the special cases that we added for JavaScript and Flow also work for TypeScript constructs. In this case, objects should also hug if they are wrapped in a as operator.

// Before
const state = JSON.stringify(
  {
    next: window.location.href,
    nonce,
  } as State
);
// After

const state = JSON.stringify({

next: window.location.href,

nonce,

} as State);

Remove parens for type assertions in binary expressions (#2419) by @azz

Most of the time we add parenthesis for correctness but in this case, we added them for nothing, so we can just get rid of them and have a cleaner code :)

// Before
(<x>a) || {};
// After

<x>a || {};

Print parens around type assertion as LHS in assignment (#2525) by @azz

Yet another case of missing parenthesis. Thankfully we're getting very few of them nowadays and they are for extremely rare edge cases.

// Before
foo.bar as Baz = [bar];
// After

(foo.bar as Baz) = [bar];

Print declare for TSInterfaceDeclaration (#2574) by @existentialism

The declare keyword doesn't do anything for interface so we never put it there. However, it felt weird if you were in a declaration file and seeing everything have declare before it except for interfaces. So now we reprint declare if it was there in the first place.

// Before
interface Dictionary<T> {
  [index: string]: T
}
// After

declare interface Dictionary<T> {

[index: string]: T

}

CSS

Normalize quotes in CSS (#2624) by @lydell

In order to get a first version of CSS to ship, we kept string quotes as is. We are now respecting the singleQuote option of prettier. The difficulty here was to make sure that we output correct code for all the crazy escapes, unicode characters, emoji, special rules like charset which only work with double quotes...

// Before
div {
  content: "abc";
}
// After

div {

content: 'abc';

}

Normalize numbers in CSS (#2627) by @lydell

Another place where we can reuse the logic we've done for JavaScript to improve CSS printing.

// Before
border: 1px solid rgba(0., 0.0, .0, .3);
// After

border: 1px solid rgba(0, 0, 0, 0.3);

Quote unquoted CSS attribute values in selectors (#2644) by @lydell

I can never quite remember the rules behind quotes around attributes so we're now always putting quotes there.

// Before
a[id=test] {}
// After

a[id="test"] {}

Add support for css keyword (#2337) by @zanza00

// Before
const header = css`.top-bar {background: black;margin: 0;position: fixed;}`
// After

const header = css</span></span> <span class="pl-s">  .top-bar {</span> <span class="pl-s">    background: black;</span> <span class="pl-s">    margin: 0;</span> <span class="pl-s">    position: fixed;</span> <span class="pl-s">  }</span> <span class="pl-s"><span class="pl-pds">;

Support styled-components with existing component (#2552, #2619) by @azz

styled-components has a lot of different variants for tagging template literals as CSS. It's not ideal that we've got to encode all those ways inside of prettier but since we started, might as well do it for real.

styled(ExistingComponent)`
  css: property;
`;
styled.button.attr({})</span></span> <span class="pl-s">  border: rebeccapurple;</span> <span class="pl-s"><span class="pl-pds">;

Trim whitespace in descendant combinator (#2411) by @azz

The CSS parsers we use do not give us a 100% semantic tree: in many occasions they bail and just give us what is being entered. It's up to us to make sure we clean this up while maintaining correctness. In this case, we just printed spaces between selectors as is but we know it's correct to always replace it by a single space.

// Before
.hello
        .<span class="pl-smi">how</span><span class="pl-k">-</span>you<span class="pl-k">-</span>doin {

height: 42;

}
// After

.hello .how-you-doin {

height: 42;

}

Strip BOM before parsing (#2373) by @azz
I still have nightmares from dealing with BOM in a previous life. Thankfully, in 2017 it's no longer a big issue as most tooling is now aware of it. Thanks @azz for fixing an edge cases related to CSS parsing.
// Before
[BOM]/* Block comment *
html {
  content: "#{1}";  
}
// After
[BOM]/* Block comment */
html {
  content: "#{1}";  
}
GraphQL
Add support for range-formatting GraphQL (#2319) by @josephfrazier
If you tried to use the range formatting feature in a GraphQL file, it would throw an exception, now it properly worked again and only reformats the piece you selected.
Add .gql file extension to be parsed as GraphQL (#2357) by @rrdelaney
At Facebook, we use .graphql extension but it looks like it's common to have .gql as well, doesn't cost a lot to support it in the heuristic that figures out what parser to use.
CLI
Support multiple patterns with ignore pattern (#2356) by @evilebottnawi
It was already possible to have multiple glob patterns but they would be additive, with this change, you can add a glob pattern to ignore some files. It should be very handy to ignore folders that are deeply nested.
prettier --write '{**/*,*}.{js,jsx,json}' '!vendor/**'
Make --list-different to work with --stdin (#2393) by @josephfrazier
This is a handy way of knowing if prettier would print a piece of code in a different way. We already had all the concepts in place, we just needed to wire them up correctly.
$ echo 'call ( ) ;' | prettier --list-different
(stdin)
$ echo $?
1

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Drop Node.js 4.x support

fs.chown on Windows support Node.js (process.getuid is not a function)?

fs.chown on Windows not supported, fs.stats return 0 for uid and gid

  × TypeError: process.getuid is not a function
  ----------------------------------------------
    operator: error

Node.js 5.3.0 on Windows 10

api shorthand options for fs.write etc.

Support pos, len, off that map to position, length, offset. Truncate already supports len.

files.write('./file.txt', 'bar', {
    pos: 4
})

Check all methods accept flag and flags. Provice enc for encoding?

support URL object as path

In Node.js v7.6.0
The path parameter can be a WHATWG URL object using file: protocol. Support is currently still experimental

Promise access, link and symlink

An in-range update of codecov is breaking the build 🚨

The devDependency codecov was updated from `3.4.0` to `3.5.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ ci/circleci: node-8: Your tests passed on CircleCI! (Details).
✅ ci/circleci: node-10: Your tests passed on CircleCI! (Details).
✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
❌ codecov/project: 91.44% (-3.32%) compared to 9b4edf7 (Details).
✅ codecov/patch: Coverage not affected when comparing 9b4edf7...5e91cce (Details).

Commits

The new version differs by 3 commits.

e98d176 v3.5.0
c7741f2 Patch cves 755 813 (#130)
03256a4 feat(services): add TeamCity CI (#131)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

test open then close twice fails on windows

related nodejs/node#3718

fildes/test/test-open.js

Lines 132 to 152 in 57c415b

    
           tape('close twice', function(t){ 
        
               file.open(filepath2) 
        
               .then(function(fd){ 
        
                   return file.close(fd) 
        
                   .then(function(){ 
        
                       t.pass('close first time'); 
        
                       return file.close(fd); 
        
                   }); 
        
               }) 
        
               .then(function(){ 
        
                   t.fail('should not close twice'); 
        
                   t.end(); 
        
               }) 
        
               .catch(function(error){ 
        
                   t.ok(error, error); 
        
                   t.equal(error.code, 'EBADF', 'error.code is EBADF'); 
        
                   t.equal(error.syscall, 'close', 'error.syscall is close'); 
        
                   t.end(); 
        
               }); 
        
           });

allow flag and flags

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

fs.writeFile Error: ENOENT: no such file or directory, open

fs.writeFile throws if directory does not exist ENOENT. fildes.writeFile should catch ENOENT: no such file or directory Error and try to create the directory and try fs.writeFile again.

var file = require('fildes');

file.writeFile('./dir/does/not/exist/yet/file.txt', 'will create parent directories')
.then(function(){
    console.log('dir created and file written');
})
.catch(function(error){
    console.error(error);
});

fs.symlink Error: EPERM: operation not permitted, symlink

Node.js needs to run as administrator to be able to create symlinks,
see nodejs/node-v0.x-archive#2274
and nodejs/node-v0.x-archive#6342

  symlink

    × Error: EPERM: operation not permitted, symlink
node_modules\fildes\test\data\symlink\symlink.txt'
    -------------------------------------------
----------------------------------------------
      operator: error
      expected: |-
        undefined
      actual: |-
        { [Error: EPERM: operation not permitted, symlink
node_modules\fildes\test\data\symlink\symlink.t
2\\test\\data\\symlink.txt', dest: 'c:\\Users\\
      stack: |-

An in-range update of eslint-config-prettier is breaking the build 🚨

Version 2.4.0 of eslint-config-prettier just got published.

Branch	Build failing 🚨
Dependency	eslint-config-prettier
Current Version	2.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-config-prettier 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 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ bitHound - Code 18 failing files. Details
✅ bitHound - Dependencies No failing dependencies. Details

Commits

The new version differs by 4 commits.

68537d1 eslint-config-prettier v2.4.0
cd99265 Fix broken link in changelog
cd84a6b Update dependencies
42dd938 Turn off function-paren-newline, introduced in ESLint v4.6.0 (#27)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of rimraf is breaking the build 🚨

Version 2.6.2 of rimraf just got published.

Branch	Build failing 🚨
Dependency	rimraf
Current Version	2.6.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As rimraf 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 💪

Status Details

❌ bitHound - Code null Details
❌ bitHound - Dependencies null Details
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 2 commits.

79b933f v2.6.2
38b907f Fix #159, correct 0o666 chmod

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

try travis-ci multi-os

http://docs.travis-ci.com/user/multi-os/

use Buffer.from?

https://nodejs.org/en/blog/release/v6.0.0/#notable-changes
nodejs/node#4682

	tape('close twice', function(t){
	file.open(filepath2)
	.then(function(fd){

	return file.close(fd)
	.then(function(){
	t.pass('close first time');
	return file.close(fd);
	});
	})
	.then(function(){
	t.fail('should not close twice');
	t.end();
	})
	.catch(function(error){
	t.ok(error, error);
	t.equal(error.code, 'EBADF', 'error.code is EBADF');
	t.equal(error.syscall, 'close', 'error.syscall is close');
	t.end();
	});
	});

thisconnect / fildes Goto Github PK

fildes's People

Contributors

Stargazers

Watchers

Forkers

fildes's Issues

The devDependency codecov was updated from 3.2.0 to 3.3.0.

The devDependency nyc was updated from 14.0.0 to 14.1.0.

The devDependency prettier was updated from 1.14.2 to 1.14.3.

Version 11.2.0 of nyc just got published.

Version 4.6.0 of eslint just got published.

Version 1.3.0 of make-dir was just published.

Version 2.3.1 of codecov was just published.

Version 1.8.2 of prettier was just published.

The devDependency codecov was updated from 3.1.0 to 3.2.0.

Version 2.3.0 of eslint-plugin-prettier just got published.

Version 3.6.0 of eslint-plugin-promise was just published.

Version 4.2.2 of prettier-eslint-cli just got published.

4.2.2 (2017-08-30)

Bug Fixes

Version 4.1.1 of eslint just got published.

Version 1.10.1 of prettier was just published.

Version 1.13.2 of prettier was just published.

Version 1.6.0 of prettier just got published.

Highlights

Configuration

Implement cosmiconfig for workspace configuration (#2434) by @azz

Support .prettierignore files (#2412) by @evilebottnawi

JSX

Improve JSX Formatting (#2398) by @suchipi

Inline single expressions in JSX (#2442) by @karl

Ensure there is a line break after leading JSX white space (#2348) by @karl

Other Changes

JSON

Use babylon.parseExpression for JSON (#2476) by @josephfrazier

JavaScript

Add more supervisory parens (#2423) by @azz

Implement prettier-ignore inside JSX (#2487) by @azz

Do not swallow prettier-ignore comments (#2664)

Fix indentation of a do-while condition (#2359) by @jsnajdr

Break sequence expressions (#2388) by @bakkot

Trim trailing whitespace from comments (#2494) by @azz

Fix interleaved comments in class decorators (#2660, #2661)

Improve bind expression formatting (#2493) by @azz

Add support for printing optional catch binding (#2570) by @existentialism

Add support for printing optional chaining syntax (#2572) by @azz

Handle Closure Compiler type cast syntax correctly (#2484) by @yangsu

Inline first computed property lookup in member chain (#2670) by @azz

Flow

Support opaque types and export star (#2543, #2542) by @existentialism

Strip away unnecessary quotes in keys in type objects and interfaces (#2643)

Print TypeParameter even when unary function type (#2406) by @danwang

Keep parens around FunctionTypeAnnotation inside ArrayTypeAnnotation (#2561) by @azz

TypeScript

Support TypeScript 2.5 RC (#2672) by @azz

Don't add namespace keyword to global declaration (#2329) by @azz

Fix <this.Component /> (#2472) by @backus

Allow type assertions to hug (#2439) by @azz

Remove parens for type assertions in binary expressions (#2419) by @azz

Print parens around type assertion as LHS in assignment (#2525) by @azz

Print declare for TSInterfaceDeclaration (#2574) by @existentialism

CSS

Normalize quotes in CSS (#2624) by @lydell

Normalize numbers in CSS (#2627) by @lydell

Quote unquoted CSS attribute values in selectors (#2644) by @lydell

Add support for css keyword (#2337) by @zanza00

Support styled-components with existing component (#2552, #2619) by @azz

Trim whitespace in descendant combinator (#2411) by @azz

Strip BOM before parsing (#2373) by @azz

GraphQL

Add support for range-formatting GraphQL (#2319) by @josephfrazier

Add .gql file extension to be parsed as GraphQL (#2357) by @rrdelaney

CLI

Support multiple patterns with ignore pattern (#2356) by @evilebottnawi

Make --list-different to work with --stdin (#2393) by @josephfrazier

The devDependency codecov was updated from 3.4.0 to 3.5.0.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

Version 2.4.0 of eslint-config-prettier just got published.

Version 2.6.2 of rimraf just got published.

The devDependency codecov was updated from `3.2.0` to `3.3.0`.

The devDependency nyc was updated from `14.0.0` to `14.1.0`.

The devDependency prettier was updated from `1.14.2` to `1.14.3`.

The devDependency codecov was updated from `3.1.0` to `3.2.0`.

Add `.gql` file extension to be parsed as GraphQL (#2357) by @rrdelaney

The devDependency codecov was updated from `3.4.0` to `3.5.0`.