-
-
Notifications
You must be signed in to change notification settings - Fork 396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renaming files with "gulp-rename" in "registerTransformStream" causes "Error: write after end" #577
Comments
This seems to be caused by recent changes in gulp-rename (current version 1.2.3). Older versions work just fine. In my case i had to pin gulp-rename to 1.2.2 to fix my generators. |
Thanks @UncleWalt, I'll close this issue then. |
@UncleWalt thanks, it works. |
I tried |
… "Error: write after end"yeoman/yo#577
This is still an issue with gulp-rename |
yeoman relevant issue: yeoman/yo#577 gulp-rename: relevant issue: hparra/gulp-rename#84
* fix(build): update typescript dep and add @types/node Updated typescript to v3.x, and add node types to fix tsc build Closes #25 * build(dependencies): update dev dependencies and related configs re #25 * improvement: update dev dependencies and related configs in default template * fix: fix tooling configs not in default * build: remove typescript (not needed) and add semantic release script * build: update babel and babelrc * test: ignore built and template tests * chore: Update yeoman dependencies and lock gulp-rename yeoman relevant issue: yeoman/yo#577 gulp-rename: relevant issue: hparra/gulp-rename#84 * test: update snapshots * ci: Test on modern nodejs version * chore: Update vscode jest debug config * ci: use yarn in travis ci * fix: downgrade commitzen, didn't work with node<=10 * refactor: remove node<10 support BREAKING CHANGE: Removed support for node<10 in the generator and the generated plugins too * fix: update babel config and dependencies in template
Still an issue with gulp-rename |
Type of issue
Bug
My environment
Windows 10 64-bit
v8.11.2
6.0.1
2.0.2
Expected behavior
Rename of a file in
registerTransformStream
doesn't cause errors.Current behavior
when I'm trying to rename a file with
gulp-rename
inregisterTransformStream
I see an error after the write method execution.Steps to reproduce the behavior
Command line output
The text was updated successfully, but these errors were encountered: