psc-package
psc-package copied to clipboard
purescript
A package manager for PureScript based on package sets
When run from cmd prompt: ``` >psc-package init Initializing new project in current directory Using the default package set for PureScript compiler version 0.11.7 (Use --source / --set to override...
We construct several directory and file paths using ``. If a package set, package or tag name has path parts in its name such as `..`, then this allows `psc-package`...
Sorry if this is already the case. Using `psc-packages` with success to build my project, but now I'm wrapping it up as a `Nix` expression, and it would help to...
Requiring a hash in addition to the version tag would be a cheap additional layer of security. As it stands, a package author could maliciously amend a tag in their...
Similar to #55. Allowing the _set_ property in _psc-package.json_ to be a commit hash would be secure against sneaky set modifications.
It would be nice if I could install packages from local cache, similar to what `bower i -o` provided
It'd be nice if you could see what package set you're using from the CLI, instead of having to tab into your editor or `cat` your psc-package.json. I figure either...
`$ purs compile -o output $(psc-package sources) 'src/**/*.purs'` will fail because `psc-package sources` outputs "\" directory separator on windows, but my bash shell (mingw) only supports "/" dir separator. Also,...
Hey there, I've `psc-package install react-basic`'d in order to try out the [react-basic counter example](https://github.com/lumihq/purescript-react-basic/tree/master/examples/counter) and there seems to be a mismatch of version. The current `psc-package set` has `react-basic`...
We should be able to publish packages to Pursuit using purs publish, by generating the two necessary JSON files in the correct format.
Metadata
Owner
Metadata
A package manager for PureScript based on package sets