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

Update package.json and publish completed build to NPM #3

Closed
5 tasks done
jasonwebb opened this issue Aug 13, 2020 · 5 comments
Closed
5 tasks done

Update package.json and publish completed build to NPM #3

jasonwebb opened this issue Aug 13, 2020 · 5 comments

Comments

@jasonwebb
Copy link

jasonwebb commented Aug 13, 2020

  • Set up official user account on npmjs.org.
  • Update package.json metadata file.
  • Publish as an NPM package.
    • Set up Github Action workflow to publish to npm when a release is published.
  • Create a Release on Github.
@agentcap
Copy link

agentcap commented Dec 3, 2020

@jasonwebb Hi! Can I know when this package is planned to be published to NPM? Thanks!

@jasonwebb
Copy link
Author

Hey @agentcap! This package will be published to NPM as soon as it has been tested by expert users with disabilities as part of issue #21. My team at @Accessible360 is currently focused on a heavy end-of-year workload as our clients are rushing to hit their 2020 targets, but after New Years I expect their availability to open up.

I would estimate that this package will be officially published before the end of January 2021.

jasonwebb added a commit that referenced this issue Jan 12, 2021
@jasonwebb
Copy link
Author

Testing has been completed with a native screen reader user, and I've finished making some small updates based on their feedback (see #21). This is now ready to officially launch!

I've created a Github workflow to publish to both npm and Github Packages registry when a new release is published.

Now I'm trying to figure out how to set up the credentials and tokens properly, which is a little more complicated since there is an org account involved.

@jasonwebb
Copy link
Author

While doing some dry runs, I learned that NPM requires strict semver naming in the package.json > version field. I was hoping to release this package with a that piggybacks on the original Slick repo's version number (1.8.1), but that does not seem possible now.

Instead I'll go ahead and use the version number 1.0.0, and indicate which Slick version this was forked from in the README.

@jasonwebb jasonwebb mentioned this issue Jan 12, 2021
9 tasks
jasonwebb added a commit that referenced this issue Jan 14, 2021
@jasonwebb
Copy link
Author

accessible-slick is now officially released!!

I had to do a bit of fussing to get the publish workflow Action to work, and learned a couple new Git tidbits along the way. Unfortunately I had to increment the version number because the package was prematurely published to NPM while I was fussing around, and NPM does not allow reuse or deletion of version numbers.

You can now grab this package and start using it right away the following ways:

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