-
Notifications
You must be signed in to change notification settings - Fork 0
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 deps, fix test coverage, linting #1
Conversation
zemccartney
commented
Apr 24, 2020
- Updates slew of deps
- Fix missing test coverage
- General linting
- Update travis node versions
Note that this work doesn't include any sort of integration yet i.e. I didn't use this updated version in a project, confirming it still works as expected. Do we have a preferred way of running such a test? |
I think the primary way to do that is to build locally then npm link it into a project. |
You could also publish a beta then allow many folks to pull it into their project to test prior to a "latest" release (in npm tag speak). This looks great, by the way—thanks! |
🙏 thanks for checking this out! Probably should have asked this at the beginning, before doing this work 🤡 : What's the future of Clearly I'm way out of touch here; sorry for the flail. Thanks for all the help! |
Oh no way, I think you are v much in touch 😏. I think strange-auth will look pretty different in the future. Half of strange-auth is allowing one to author an async action given just an async function: now that is all taken care of generically by strange-middle-end. I think you're dead on that strange-auth will look like a plugin, which in our case is a mod-creator (i.e. a function returning a strange-middle-end mod). |
🎩 🎩 🎩 |
Closing since effectively blocked till we sort out strange-auth's next direction |