Prerelease on npm

[penx]

It's coming up on 2 years since [email protected] was released to npm.

@whitlockjc any chance you could put the current master as a prerelease on npm?

I think this is all that's needed:

npm version prerelease
npm publish

It would help me a lot with building and releasing tooling that requires a recent version of sway 🙂

[whitlockjc]

Any reason you can't use apigee-127/sway@master?

[penx]

Our team's issue is that we need to npm install from our internal package repository rather than from npm directly and users won't have access to GitHub when this happens.

sway, swagger-node-runner etc. all need to be mirrored on our internal package repository and at some point patched with the changes I have on my forks. As far as I can tell, the easiest way to do this would be to import a release candidate from npm and then use patch-package to apply any further changes I need.

If you're interested, I've raised PRs for the changes I've made in my forks and am tracking them here:
penx/openapi-mock#5

Lastly thanks for your work on this 🙂

[jwalton]

Could we even have a 1.1.0 release? I'm using swagger-node-runner which relies on Sway. Would be nice if I could get access to custom formats.

[whitlockjc]

Crafting a 1.1.0 release right now should be possible but I'd need to figure out what things could be merged. Do you see anything in the release notes that would be breaking and require a 2.0.0 vs. a 1.1.0? 1.0.1 definitely isn't an option with everything in the release notes.

[whitlockjc]

I'm going to treat this as a duplicate of #176 as we'll likely address this there.