npx @wedgekit/scripts <command>
MUST HAVE NODE v14+
Application vs Package Development
@wedgekit/scripts can be used to develop both A2W applications and Wedgekit packages (libraries). The following commands are valid for both application and package development; they will have different effects depending on the type of development.
The default type of development is application development. To indicate you are using a package, use the
--package flag with any of the following commands. Alternatively, use the
--script flag with any of the following commands to indicate you are using a node script.
-h after either the application name or any of the commands will pull up a help menu*.
$ npx @wedgekit/scripts create <name> /
$ wedgekit create <name>
Creates a new web application
create is only configured for web applications. Package creation is coming someday*.
|name||The web application name; a directory will be created with this name|
||Defines the location of the application if different from
||Adds a description of the application/package|
||Makes the created application with the specified template possible options are
$ npx @wedgekit/scripts build /
$ wedgekit build
Build the src directory. Expects an
src/index.ts entry file.
||Only builds type declaration files; used for type-only packages|
||Distributes the unbundled files in addition to the ESM and CJS bundles|
||Watches source files for changes that would invalidate the build and rebuilds|
$ npx @wedgekit/scripts start /
$ wedgekit start
Starts a dev server for local app development if in app mode. Expects an
index.html in the current working directory. If in script mode, runs the script in
start is only intended for use with web applications and scripts. Package developers should use
wedgekit build -w instead.
vite flags will be applied to
wedgekit start. For a list type
npx vite --h
proxy flag is necessary to use samesite cookies locally
||Uses the Vite proxy middleware to proxy to the desired graphql environment|
||Uses the Vite proxy middleware to proxy to the desired rest environment|
someday - The long-promised day in which all prioritized features will be complete and developers can tackle long-delayed tech debt.
soon - As soon as all urgent work is complete, which is a state of existence which will surely be upon us any day now.