Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support purs publish #43

Open
paf31 opened this issue Jul 12, 2017 · 4 comments
Open

Support purs publish #43

paf31 opened this issue Jul 12, 2017 · 4 comments

Comments

@paf31
Copy link
Contributor

paf31 commented Jul 12, 2017

We should be able to publish packages to Pursuit using purs publish, by generating the two necessary JSON files in the correct format.
@hdgarrood
Copy link
Contributor

Does this raise an issue about what a given package name on Pursuit refers to? Currently it's safe to assume that if a package appears on Pursuit, and you bower install it, you get the same package that you saw, and I think it might be a shame to lose that.

@paf31
Copy link
Contributor Author

paf31 commented Jul 17, 2017

Hmm, this is a good point. I'll think about it.

@matthewleon matthewleon mentioned this issue Aug 5, 2017
Closed
Rembane pushed a commit to Rembane/psc-package that referenced this issue May 26, 2018
@paf31
Use the current branch, fix purescript#43 (purescript#44)
c33733a 
* Use the current branch, fix purescript#43

* Update .travis.yml

* Update .travis.yml

* Use a script
@dakom
Copy link

dakom commented Aug 27, 2018

What is the recommended approach for publishing to pursuit now? It seems pulp relies on there being a bower.json, but having a dummy bower.json (just for pursuit) causes builds to fail due to missing dependencies

@hdgarrood
Copy link
Contributor

For now you should put together a real bower.json and publish to Bower when publishing to Pursuit, so that your package can be used by people using Bower as well as people using psc-package.

@JordanMartinez JordanMartinez mentioned this issue Aug 28, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@paf31 @hdgarrood @dakom