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
Error: write after end #84
Comments
I'm having the same issue |
If you wish a quickfix @alvaromartmart, you can use v1.2.2 meanwhile:
|
|
Still an issue with v2.0.0. With 1.2.2 it works for me. |
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
Having same issue, and what I've noticed is that it seems to be caused when you make changes to file object that is cloned In my case I got it working by replacing gulp-rename with:
This seems to be working and I'm not getting any errors. As soon as I add |
This is still an issue. Downgrading to <=1.2.2. worked for me |
+1 - stream never ending in 1.4.0 when file source >= 100k (approximately) |
Cam everyone who is having issues post what version of node you are using? |
had issue with both node 8 and 10 |
@bendenoz Can you try it with the latest version of node and see if that resolves it? Node 8 is a year past end of life as well so not something we're trying to support right now, but node 10 not working is something we will fix if its an issue there. |
As another thing you could try if you want to be a guinea pig - on line 3 of this package replace |
@contra , readable-stream doesn't change anything, but the problem seems to lie in the originalFile.clone call. The file is created by an old version of gulp-util / vinyl so it might be part of the problem |
suryadev99 |
Hello,
I am trying to use this package as a stream for a Yeoman generator, to rename gitignore files on the fly:
https://yeoman.io/authoring/file-system.html#transform-output-files-through-streams
The error received in the terminal seems to come from
readable-stream
:Error [ERR_STREAM_WRITE_AFTER_END]: write after end
Related issue on yeoman repository:
yeoman/yo#577
The code posted above works fine with
gulp-rename@1.2.2
, but not with any more recent version.I am wondering if you are aware of this issue, and what would be the difference. According to my very quick scan on the source code, I have only seen newer dependencies versions and a LICENSE file... Not sure exactly what is the cause of this issue.
v1.2.2 dependencies:
v1.4.0 dependencies:
I am also wondering if tthose differences between version
1.2.2
and the more recent ones such as the1.4.0
currently published on NPM are accessible somewhere?https://www.npmjs.com/package/gulp-rename?activeTab=versions
Those new versions do not seem to be available as releases on this repository:
https://github.com/hparra/gulp-rename/releases
The text was updated successfully, but these errors were encountered: