Last 12 weeks · 0 commits
5 of 6 standards met
I've noticed that the UMD build contains a source map, so it could be smaller. It would be cool because you recommend to add it to Git, instead of installing from npm. I'll be happy to send a PR that either: Disables source maps in the current webpack config; Uses microbundle instead of webpack (it's based on Rollup and supposed to make smaller files). What do you think?
Repository: kentcdodds/workshop-setup. Description: Verify and setup a repository for workshop attendees Stars: 41, Forks: 3. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Homepage: https://unpkg.com/workshop-setup/dist/bundled/index.js Latest release: v3.0.0 (6y ago). Open PRs: 0, open issues: 2. Last activity: 5y ago. Community health: 71%.
The system verification logic seems incredibly useful but also infinitely extensible. I think it would be extremely useful to have a consistent template for implementing these for arbitrary system-level dependencies that takes the different operating systems into account and provides helpful error messages (e.g. pointing out the nodesource repository when a node check on Linux fails or simply pointing users to the official download page for their OS). Instead of adding these individually to this module (which will require a lot of subjective judgement on whether they should be included in the "core" or not) maybe we can extract a consistent spec/API for them and publish them individually on npm and group them via an ecosystem tag.
Simple use cases like this would be good, and I'd also like to support complex use-cases like this. Things are already set up for this feature because we're definitely doing this: Source here Tests here