Replace gulp #107

Closed
opened 2022-09-04 02:35:12 +00:00 by norm · 4 comments
Owner

Gulp doesn't seem to be actively maintained anymore:

  • The last commit is from 2021-06-22 with prior commits being very infrequent.
  • The last tagged release is v4.0.2 from 2019-05-06 which is what is currently used in Foundkey.

Much of the build process these days uses tsc directly (backend, sw, foundkey-js) or uses vite. Gulp only really seems to be used to copy certain files around to specific locations here.

Gulp doesn't seem to be actively maintained anymore: - The last commit is from [2021-06-22](https://github.com/gulpjs/gulp/commit/818bd73e5da1ad69f43eef84214c98d6392a73e4) with prior commits being very infrequent. - The last tagged release is [v4.0.2 from 2019-05-06](https://github.com/gulpjs/gulp/releases/tag/v4.0.2) which is what is currently used in Foundkey. Much of the build process these days uses `tsc` directly (backend, sw, foundkey-js) or uses `vite`. Gulp only really seems to be used to copy certain files around to specific locations here.
norm added this to the (deleted) project 2022-09-04 02:35:18 +00:00
Owner

I've not looked at the details there, and the copying does need to happen.
Would we want to do that in just some script?
If so, the script could actually invoke the dependency tree too ala redo.
What's suggested in general?

I've not looked at the details there, and the copying does need to happen. Would we want to do that in just some script? If so, the script could actually invoke the dependency tree too ala redo. What's suggested in general?
Author
Owner

I've not looked at the details there, and the copying does need to happen.
Would we want to do that in just some script?

I think that's probably the simplest way to go about it.

If so, the script could actually invoke the dependency tree too ala redo.

The script could probably just be executed after running the build task for each workspace like what's currently done with gulp.

I did notice there were a few postprocessing steps that were being done as well in the gulpfile, but I'm not really sure what would be a good way to replace those.

> I've not looked at the details there, and the copying does need to happen. Would we want to do that in just some script? I think that's probably the simplest way to go about it. > If so, the script could actually invoke the dependency tree too ala redo. The script could probably just be executed after running the build task for each workspace like what's currently done with gulp. I did notice there were a few postprocessing steps that were being done as well in the gulpfile, but I'm not really sure what would be a good way to replace those.
Owner

Maybe I'm missing the point here, but why exactly do we have to replace gulp? Does it not being maintained even mean anything for us as long as it still works?

Maybe I'm missing the point here, but why exactly do we have to replace gulp? Does it not being maintained even mean anything for us as long as it still works?
Author
Owner

Fair enough. I'll close this for now and maybe revsit this if it stops working in a significant way.

Fair enough. I'll close this for now and maybe revsit this if it stops working in a significant way.
norm closed this issue 2022-09-05 15:40:00 +00:00
norm removed this from the (deleted) project 2022-09-12 00:27:37 +00:00
Sign in to join this conversation.
No Label
feature
fix
upkeep
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: FoundKeyGang/FoundKey#107
No description provided.