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

Prep and Publish v0.0.1 #2

Closed
3 tasks done
Ethan-Arrowood opened this issue Dec 11, 2019 · 3 comments
Closed
3 tasks done

Prep and Publish v0.0.1 #2

Ethan-Arrowood opened this issue Dec 11, 2019 · 3 comments

Comments

@Ethan-Arrowood
Copy link
Member

Ethan-Arrowood commented Dec 11, 2019

Couple things necessary before we publish the initial version of this module.

  • Set up CI (either using Azure Pipelines or GitHub actions)
  • Add error cases + tests
    • i.e. invalid functions arguments
    • i.e. directory already exists
  • figure out build->deploy process
    • module is written in TypeScript so when we publish we need to publish the build directory output rather than the src directory.
@Ethan-Arrowood Ethan-Arrowood changed the title Publish v0.0.1 Prep and Publish v0.0.1 Dec 11, 2019
@Ethan-Arrowood
Copy link
Member Author

Ethan-Arrowood commented Dec 16, 2019

@fastify/fastify can someone help me with setting up CI for this repo-or just point me in the right direction? I know we've been using GitHub Actions instead of Azure Pipelines. Happy to use Actions just need to know where to start setting it up for this repo 😁

@fastify/leads what is the process of getting this module published on npm? Everything should be good to go in the package.json (prepublish command, main code path, and types path). I think I have the ability to publish to certain fastify modules on npm but not sure what to do for an initial release.

And last note: if someone has a better idea for the name of this module let me know. Welcoming other ideas before we do the initial publish!

@mcollina
Copy link
Member

CI config

Just configure github actions and you should be good to go. There is no admin task needed to do that, you should be able to add the config file here and they should kick in.

Publishing on npm

publish on npm and then add me or @delvedor, we'll add it to the org.

Naming

I think this module name is just fine. I'm really bad at names and this does what it says.

Versioning

I would release v0.1.0.

@Ethan-Arrowood
Copy link
Member Author

v0.1.0 has been released

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

No branches or pull requests

2 participants