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.

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

Integration with Parcel? #134

Open
JordanMartinez opened this issue Mar 12, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@JordanMartinez
Copy link
Contributor

commented Mar 12, 2019

Low priority.

Coming from this comment:

This [built-in browserify command] is a common use-case (also in my usage), and I've been thinking of providing some opinionated integration with parcel. Could you open an issue about it so we can discuss it there?

For context, I was only pointing out that spago doesn't currently have some sort of browserify-like built-in command. (I probably could have done a better job explaining that). So, this is not a request specifically for browserify.

It seems like parcel is a better option, so integrating parcel into spago sounds helpful. Still, it might be a bad idea. Since one can easily take the output of spago and push it into parcel, is this really necessary?
Without such integration, spago might be a better overall solution to dependency management when other backends are considered. (In making this statement, I don't know what other backends use to get their PureScript dependencies. However, downloading the source code via spago and allowing other backend-specific build tools (e.g. parcel) to do target-language-specific build-things seems like a good idea.)

@f-f

This comment has been minimized.

Copy link
Member

commented Mar 15, 2019

Given that most of the PureScript projects I've seen end up using some kind of JS dependency and in the end need a bundler, I think some kind of integration with some bundler would be useful (the reason is "less moving parts that you have to integrate yourself")

I think there are mainly two roads here:

  1. have a spago bundle-js command, that is not much more than spago build && parcel build index.html that you'd do yourself.
    I think it's OK to be opinionated and pick parcel here, in the same way pulp picks browserify
  2. or go the other way around and build an integration into parcel, so that you'd do parcel build whatever, and it would compile your PS stuff automatically (through spago or any other tool the integration wants to support). I think this would be cool, and e.g. Elm has this kind of integration (PR that implemented that is here, ~500 lines of JS)

@f-f f-f changed the title Feature Request: integration with Parcel ? Integration with Parcel? Mar 15, 2019

@JordanMartinez

This comment has been minimized.

Copy link
Contributor Author

commented Mar 15, 2019

I think the second approach makes more sense. It'd also make things easier for those coming from the JS world. This same approach could potentially be done for other backends as well.

@f-f f-f added the help wanted label Mar 15, 2019

@f-f f-f added the blocked/upstream label May 5, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.