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

Publish our new package template as a standalone tool that everyone can use #3900

Closed
KyleAMathews opened this issue Feb 7, 2018 · 15 comments

Comments

@KyleAMathews
Copy link
Contributor

To add a new package to this repo, you can run npm run plop and then choose package and then it sets up a new package for you — see https://github.com/gatsbyjs/gatsby/tree/master/plop-templates/package

It'd be cool to have a standalone tool for others to use when creating a new plugin to distribute as it's not always obvious how to create new NPM packages and publish them.

This along with a short tutorial on publishing a new NPM package would be 🔥

@shannonbux
Copy link
Contributor

shannonbux commented Feb 7, 2018

This is the #3 most wanted thing in Gatsby tutorials. A tutorial on how to create and/or modify an existing plugin (same as package, sort of?). Making it easy to create packages and publish them would be top notch.

@m-allanson
Copy link
Contributor

m-allanson commented Feb 9, 2018

Maybe this could be rolled into gatsby-cli?

Being able to do gatsby plugin my-new-plugin could be nice.

@KyleAMathews
Copy link
Contributor Author

@m-allanson that makes sense!

@shannonbux
Copy link
Contributor

@KyleAMathews I'm thinking of adding this to docs projects. Does that make sense?

@KyleAMathews
Copy link
Contributor Author

@shannonbux 👍

@shannonbux shannonbux added this to In progress in Documentation Project Feb 9, 2018
@shannonbux shannonbux moved this from In progress to To do in Documentation Project Feb 9, 2018
@shannonbux
Copy link
Contributor

Summary of what interviewees said about needing help building their own packages/plugins: https://slack-files.com/T6VN36NMP-F8RP27E4A-928a785a43

@Jaikant
Copy link
Contributor

Jaikant commented Feb 10, 2018

@m-allanson I prefer npm install as it gives me the native feel of react and npm. Enhancing the cli though could help those not familiar to npm. I also prefer a git clone and npm install instead of doing a gatsby new. So maybe it is only me.

@Redmega
Copy link

Redmega commented Feb 10, 2018

All good points @shannonbux

For the record, I strongly identify with:

People coming from React might need to know when they need a plugin vs. when can they do something natively

@shannonbux
Copy link
Contributor

@benjaminhoffman have you seen this?

@benjaminhoffman
Copy link
Contributor

love this. thx for the ping. going thru the steps to create a plugin now. hopefully have it wrapped up in a week or so and will write a 'how to post'.

@shannonbux shannonbux moved this from To do to In progress in Documentation Project Feb 28, 2018
@shannonbux shannonbux moved this from In progress to To do in Documentation Project Feb 28, 2018
@shannonbux
Copy link
Contributor

Will this be closed once @jlengstorf plugin work is done (the tutorial, the sample READme template thing, etc.)?

@shannonbux
Copy link
Contributor

@KyleAMathews a lot of people liked this idea, wondering when/if to bring it back into people's minds!

@KyleAMathews
Copy link
Contributor Author

Definitely still worth doing!

@jlengstorf
Copy link
Contributor

This should be rolled up into the CLI work that I still need to define.

@KyleAMathews
Copy link
Contributor Author

Due to the high volume of issues, we're closing out older ones without recent activity. Please open a new issue if you need help!

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

No branches or pull requests

7 participants