Add to psc-package set? about purescript-spec HOT 5 CLOSED

Hey, sorry to kept this issue lying around so long. I'm not using psc-package so I'm not sure how it would work and how much work it would be to keep them in sync. Sadly, I'm not using PureScript at all at the moment and my time is stretched thin for OSS work. If we add a psc-package.json, do you think it could become a problem (e.g. becoming outdated)?

from purescript-spec.

Hey, Sorry here too. There are two ways in which it can become outdated:

• refers to an old version of the package set
• misses a dependency that gets added

Both should be less work than updating bower.json (which unfortunately also still appears to be necessary) with all it's version bounds (my workflow there is run npm-check-updates and hope for the best)

In a way, having a psc-package.json is somewhat duplicated, since it is in the package set, where the dependencies are also listed (and the version of the package set is inherent). I think it just makes it that bit easier to check out the project from source and work on it.

(In the meantime bower gets more and more deprecated. Installing it now gives a warning to install yarn and convert the bower file to yarn, but on the yarn end support for bower appears to have been dropped, I can dig up the links if desired).

from purescript-spec.

All right. Yeah, I think you can add it then. 👍

from purescript-spec.

This could be closed now I think since psc-package has this 🎉

from purescript-spec.

I was thinking the same thing, but didn't have time to check 🎉

from purescript-spec.