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

Add some tutorials for JS development #1002

Open
f-f opened this issue Sep 19, 2023 · 3 comments
Open

Add some tutorials for JS development #1002

f-f opened this issue Sep 19, 2023 · 3 comments

Comments

@f-f
Copy link
Member

f-f commented Sep 19, 2023

The docs used to contain some tutorials for getting a small JavaScript project up and running with various bundlers and setups.

Over time that section grew to take a considerable chunk of the docs, and it was unwieldy to maintain, so it was dropped during the rewrite of the docs.

I am not sure at all if we should include such extensive documentation for how to bootstrap a project, as it feels like it would be more suited for inclusion in the cookbook and we could just redirect there? (cc @JordanMartinez)

@JordanMartinez
Copy link
Contributor

That might be a good idea. At the very least, the new spago is the kind of tool I wanted for the cookbook, as each recipe is technically its own package.

@f-f f-f mentioned this issue Jan 15, 2024
@flip111
Copy link
Contributor

flip111 commented Jan 18, 2024

It would also be good if it were easy to switch to a production build. Sure there is bundle but the output file still has to be wired up. Also production builds can require different backends like recommended here https://github.com/aristanetworks/purescript-backend-optimizer Not sure how this scenario can be implemented in the new spago

@fsoikin
Copy link
Collaborator

fsoikin commented Sep 21, 2024

That documentation seems indeed super extensive to me. For example, if you're starting a whole new project, why would you use non-latest version of PureScript? And the different bundlers with so much configuration. For a basic "get up and running" setup, it seems to me, just spago init is enough. And even if you wanted to make a web app, - for example, our Elmish getting started guide fits on one screen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants