Skip to content

Update 'Editor and tool support' Guide to reflect current status #296

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

Conversation

mbbx6spp
Copy link
Contributor

This updates the list of build tools and package managers for PureScript in the 'Editor and tool support' guide based on last activity witnessed in linked repositories, splitting the tools into the categories:

  • maintained and actively supported
  • deprecated (due to repositories slightly staling)
  • unmaintained (due to either maintainer stating it was unmaintained or no commits on mainline in last 1.5 years)

- [Gulp task](https://github.com/purescript-contrib/gulp-purescript) (`gulp-purescript` in `npm`). *Spago is recommended over the PureScript Gulp task.*

Unmaintained:
- [psvm-js](https://github.com/ThomasCrvsr/psvm-js) - PureScript Version Manager
- [psc-pane](https://github.com/anttih/psc-pane) - Auto reloading compiler which formats a single error to fit the window
- [purescript-psa](https://github.com/natefaubion/purescript-psa) - A pretty, flexible error/warning reporting frontend for `psc` featuring colours, original source spans in errors, warning filtering and persistence.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

psa is not unmaintained, it just does everything it needs to and does it well. It's the first thing we recommend when users ask for better error output and configuration of warnings.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additionally, psa is backed by psa-utils which pscid and the lsp implementations rely on.

@hdgarrood
Copy link
Collaborator

Thanks for this - this page definitely does need updating. However, I don’t think it’s safe to designate things as ‘unmaintained’ or even ‘deprecated’ just on the basis of GitHub history. Along the same lines - my understanding of the word “deprecation” is that it means that the authors or maintainers have stated that they do not intend to continue to work on the thing and that they recommend using an alternative, so it isn’t a label that you can really apply to other people’s projects without their input.

Pulp isn’t deprecated either. I do plan to deprecate it eventually but at the moment it is the only tool I’m aware of which can publish packages to Pursuit, and we can’t deprecate it until there’s an alternative (which will likely be Spago, soon).

I’ll have a think about how I’d like to proceed here and get back to you.

@mbbx6spp
Copy link
Contributor Author

mbbx6spp commented Mar 2, 2020

@hdgarrood @natefaubion Totally fair. I added a new change and kept only two in the unmaintained list (one is stated as not maintained by the author and the other has not had any activity in 2.5 years with outstanding issues for 4 years also). I moved the psa link up to maintained. See 7d291e9. Happy to make more changes too.

Copy link
Collaborator

@hdgarrood hdgarrood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thanks!

@hdgarrood hdgarrood merged commit 446cc55 into purescript:master May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants