This is archived because I don't have time to work on it or maintain it, but feel free to explore/fork/etc.
by kentcdoddsJavaScript
Last 12 weeks · 0 commits
3 of 6 standards met
Repository: kentcdodds/slice-js. Description: This is archived because I don't have time to work on it or maintain it, but feel free to explore/fork/etc. Stars: 17, Forks: 8. Primary language: JavaScript. Languages: JavaScript (99.2%), HTML (0.8%). License: MIT. Homepage: https://www.youtube.com/watch?v=enlfQRUXb-s&list=PLV5CVI1eNcJgNqzNwcs4UKrlJdhfDjshf Open PRs: 0, open issues: 5. Last activity: 7mo ago. Community health: 57%. Top contributors: kentcdodds.
Like here and here. In those cases the previous call to returns an object that has the AST which we could transform directly with . But I had trouble doing that for some reason... Another thing that would be cool to figure out, but I had trouble is if we could apply all the plugins at the same time, or at least the dead code elimination ones....
One of the coolest implications of SliceJS is removing code creates objects and variables which are never actually used in the slice. In those cases we could actually remove the instantiation of those variables and properties. I call this data shaking (maybe it should be called "variable shaking"? Anyway, as far as I know, there's currently no tool that instruments JavaScript for data coverage, so we will have to build it ourselves. This project could even be a separate effort from SliceJS and have even wider implications itself. Anyone up for the task?
Should we use Lerna? This project is going to have quite a few other related projects. Editor plugins, utils/helper modules, webpack/browserify/etc. plugins. Should implement Lerna right now and save ourselves some trouble in the future? Eventually I'll definitely want this to be set up with semantic-release (when it's actually open sourced), can I use that with Lerna?