Skip to content
This repository was archived by the owner on Mar 31, 2025. It is now read-only.

fix(base): ensure writeFile() actually writes files to disk#288

Merged
petebacondarwin merged 1 commit into
masterfrom
mkdirp-update
Feb 12, 2020
Merged

fix(base): ensure writeFile() actually writes files to disk#288
petebacondarwin merged 1 commit into
masterfrom
mkdirp-update

Conversation

@petebacondarwin

Copy link
Copy Markdown
Contributor

The mkdirp-promise dependency had its own dependency of
"mkdirp": "*". But recently mkdirp did a new breaking change
release that is no longer compatible with mkdirp-promise.
This was causing the writeFile() service never to resolve its own
promise, which resulted in files not getting written to the disk.

This commit removes the dependency on mkdirp-promise
since mkdirp now supports returning a promise directly.

Fixes #287

The `mkdirp-promise` dependency had its own dependency of
`"mkdirp": "*"`. But recently `mkdirp` did a new breaking change
release that is no longer compatible with `mkdirp-promise`.
This was causing the `writeFile()` service never to resolve its own
promise, which resulted in files not getting written to the disk.

This commit removes the dependency on `mkdirp-promise`
since `mkdirp` now supports returning a promise directly.

Fixes #287
@petebacondarwin petebacondarwin merged commit eda95f7 into master Feb 12, 2020
@petebacondarwin petebacondarwin deleted the mkdirp-update branch February 12, 2020 12:24
@wszgrcy

wszgrcy commented Apr 20, 2020

Copy link
Copy Markdown

yes!!!! I trace many codes and find mkdirp has changed but the mkdirp-promise not lock version. fuck.......

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No files are written: mkdir@1.0.0 broke mkdir-promise as such writeFile processor broke

3 participants