Skip to content

How can we make packs extendable? #5

@sunil-sandhu

Description

@sunil-sandhu

Let's begin with an example:

We have a developer by the name of Jo. Jo regularly uses Starter Pack to create a project whenever they start something new. For the sake of argument, let's say that Jo often creates a React + TypeScript app. Whenever they create this app, the first thing they end up doing is installing their favourite CSS-in-JS library, along with a router and a state management library. After doing so, Jo creates a few files for handling routing and state management.

Because Jo repeats these same tasks every time they create a new React + TypeScript app, is there a way that Jo could create some sort of script or whatever that can be executed when using Starter Pack, so as to create the React + TypeScript app, along with all the additional bits that Jo ends up doing every time?

Is there something that Jo could chain on to the end of the npx @starter-pack/cli execution? Is there something that could be read from a starterpk.config.js or .starterpackrc file or something along those lines?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions