Suppose I want to mostly use the
webapp preset as-is, but I want to modify the
'build' task (maybe to build scss or codepen examples before ts). How should I do that?
Related question: how do I know the names of the existing tasks provided by a preset?
For certain task factories (especially webpack and jest, maybe others), it should be possible to pass in config options which are mixed in with the defaults. Some possible ways to do this:
Currently, the way to set the project being operated on by
upgradePackageTask is to set
just-scripts-utils/paths. It would be clearer to pass the project path as an optional parameter to a task factory instead. (The default would still be
Currently if you want to build sass files, you can't just use the
webapp task preset, and multiple manual config modifications are required (build, webpack, jest). We should provide an easier way to handle that.
There are two types of scenarios we may want to support for building/bundling sass files
Some specific tasks in just-scripts have peer dependencies which we haven't found a good way to declare (since there is no "optional peer dependencies" field in package.json)--for example,
webpackTask requires that the consumer of
just-scripts also have
We should establish a patte