-
Notifications
You must be signed in to change notification settings - Fork 8
Support for multiple versions of purescript #50
Comments
It's true that I wonder if taking the approach of installing the purescript npm package at one's desired purescript version, and then installing a compatible version of |
I would say so, given that the module can be installed locally, i.e. a project can specifiy the purescript versions that are capable of building it. |
Agreed. Are there any changes necessary? For example, should we add documentation to describe this scenario further? |
I guess we could add a feature that allows specifying a version range by reading a field from the project's |
I agree that using the We could add a compatibility table to the readme or have |
It seems like this might be a use case for |
I agree that the idea of However, my hesitation is that I don't know if we can assume the user wants to install the purescript NPM package. For instance, they could just have an old version of purescript on their system and want to use that. If we add a Not sure if this is a bad thing. It might actually be the best approach to ensure proper version compatibility. Also, if the user is on npm@3, having the peer dependency is even better because it does not force installing anything. It will just give a warning. I am open to discussing this further and hearing others' thoughts on this approach. |
Necro'ing a thread here, but in case someone else reads this:
Good call. Said package doesn't work on CentOS 6, for example, and wouldn't work with testing a new (unreleased) version of PureScript; it really can't be assumed that people can use the |
As per your README:
This has the disadvantage that projects are dependent on a command in their PATH called
psc
etc that happens to be purescript and happens to be at a specific version. Seeing that purescript is on npm, would it not be feasible to tellgulp-purescript
either the semver of purescript to use, or provide a path to the binary? I do understand that their is a certain degree of coupling betweengulp-purescript
and the actual purescript version - i.e. commands are added / renamed / removed. But if we added this now, at least for the future we could choose to stick with an older version of purescript andgulp-purescript
if a project maintainer chose to.The text was updated successfully, but these errors were encountered: