thomashoneyman
commented
4 years ago @ethul pinging you just in case you weren’t notified via watching the repository; I didn’t notice other authors to also loop in but if you’re aware of others who should be explicitly mentioned please feel free to! Thanks!
We are considering deprecating this library as part of a purescript-contrib cleanup -- see the full discussion on Discourse for more details on the effort.
"Deprecation" means that this library either moves to a private maintainer or is moved to the purescript-deprecated organization and made read-only. If the library is deprecated it can still be installed but it won't receive future updates. Projects using gulp-purescript can continue using it in its current state.
gulp-purescript has been supplanted by tools like Pulp and Spago as build tools and Webpack and Parcel as bundlers as the de facto choice for PureScript projects in the last few years. And while GitHub's "Used by" interface lists 173 projects, when we actually reviewed those projects we almost all of them (and all of the tools) have since stopped using gulp-purescript.
The PureScript ecosystem largely moved away from Gulp in 2015:
-profunctor)There are still projects using gulp-purescript, but which haven't been updated in a long time and are not compatible with any recent compiler versions (most of these are in the 0.7 - 0.10 compiler ranges; we're about to release 0.14):
Finally, some projects use gulp-purescript and have been written or update since 2018, but would be able to continue using the archived / deprecated library:
Please feel free to weigh in on this discussion either here or in the Discourse discussion.