Gathering detailed insights and metrics for @bobyzgirlllnpm/voluptate-itaque-quae
Gathering detailed insights and metrics for @bobyzgirlllnpm/voluptate-itaque-quae
Gathering detailed insights and metrics for @bobyzgirlllnpm/voluptate-itaque-quae
Gathering detailed insights and metrics for @bobyzgirlllnpm/voluptate-itaque-quae
npm install @bobyzgirlllnpm/voluptate-itaque-quae
Typescript
Module System
Node Version
NPM Version
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
30
task runner and toolkit extending SvelteKit 🌰 generate, run, optimize
npm i -D @bobyzgirlllnpm/voluptate-itaque-quae
Windows won't be supported, I chose Bash instead
Gro is a task runner and toolkit extending SvelteKit, Vite, and esbuild for making web frontends, servers, and libraries with TypeScript. It includes:
*.task.ts
@sveltejs/package
for the library$lib
$lib
, $env
, and $app
in tasks, tests, Node servers,
and other code outside of the SvelteKit frontend,
so you can use SvelteKit patterns everywhere
(these are best-effort shims, not perfect)gro run a.ts
fuz_template
for a simple starter project example, and
@feltjs/felt
for a more complex example with custom tasksuvu
gen
@feltjs/eslint-config
)Task
runner
uvu
gen
code generationpublic
package features (nonstandard)depends on node >=20.10
Typical usage installs @bobyzgirlllnpm/voluptate-itaque-quae as a dev dependency:
1npm i -D @bobyzgirlllnpm/voluptate-itaque-quae 2npx gro
It's handy to install globally too:
1npm i -g @bobyzgirlllnpm/voluptate-itaque-quae 2gro
Gro has a task runner that discovers and runs TypeScript modules with the .task.
subextension.
Running gro
with no args prints the tasks
it finds in the current directory along with its builtin tasks:
1gro # prints available tasks - defers to any local gro installation
Run a task: gro [name]
View help: gro [name] --help
17 tasks in gro:
build build the project
changeset call changeset with gro patterns
check check that everything is ready to commit
clean remove temporary dev and build files, and optionally prune git branches
commit commit and push to a new branch
deploy deploy to a branch
dev start SvelteKit and other dev plugins
format format source files
gen run code generation scripts
lint run eslint
publish bump version, publish to npm, and git push
release publish and deploy
run execute a file with the loader, like `node` but works for TypeScript
sync run `gro gen`, update `package.json`, and optionally `npm i` to sync up
test run tests with uvu
typecheck run tsc on the project without emitting any files
upgrade upgrade deps
Gro matches your CLI input against its filesystem conventions. It tries to do the right thing, where right is helpful but not surprising, with some magic but not too much:
1gro # print all available tasks, those matching `src/lib/**/*.task.ts` and Gro's builtins 2gro some/dir # list all tasks inside `src/lib/some/dir` 3gro some/file # run `src/lib/some/file.task.ts` 4gro some/file.task.ts # same as above 5gro a # run `src/lib/a.task.ts` if it exists, falling back to Gro's builtin 6gro a --help # print info about the "a" task; works for every task
Gro has a number of builtin tasks that you can run with the CLI. To learn more see the task docs and the generated task index.
1gro dev # start developing in watch mode 2gro dev -- vite --port 3003 # forward args by separating sections with --
1gro build # build everything for production
Testing with uvu
,
including shims for SvelteKit modules:
1gro test # run all tests for `*.test.ts` files with `uvu` 2gro test filepattern1 some.test another.test 3gro test -- uvu --forwarded_args 'to uvu'
Check all the things:
1gro check # does all of the following: 2gro typecheck # typecheck JS/TypeScript and Svelte 3gro test # run tests 4gro gen --check # ensure generated files are current 5gro format --check # ensure everything is formatted 6gro lint # eslint
For a usage example see the check.yml
CI config.
Formatting with prettier
:
1gro format # format all of the source files using Prettier 2gro format --check # check that all source files are formatted
Codegen with gen
:
1gro gen # run codegen for all `*.gen.*` files 2gro gen --check # error if any generated files are new or different
To deploy: (also see src/lib/docs/deploy.md
)
1gro deploy # build and push to the `deploy` branch
To publish: (also see src/lib/docs/publish.md
)
1gro publish # flush changeset to changelog, bump version, publish to npm, and git push
Etc:
1gro clean # delete all build artifacts from the filesystem 2gro clean --sveltekit --nodemodules --git # also deletes dirs and prunes git branches 3gro upgrade excluded-dep-1 excluded-dep-2 # npm updates to the latest everything
1gro --version # print the Gro version
For more see src/lib/docs/task.md
and src/lib/docs
.
1npm i 2npm run build # build and link `gro` - needed only once 3gro build # same as `npm run build` when the `gro` CLI is available 4gro test # make sure everything looks good - same as `npm test` 5gro test some.test another.test 6 7# use your development version of `gro` locally in another project: 8gro build # updates the `gro` CLI, same as `npm run build` 9cd ../otherproject 10npm link ../gro # from `otherproject/` 11gro build # from `../gro` on changes
Gro builds on TypeScript ∙ Svelte ∙ SvelteKit ∙ Vite ∙ esbuild ∙ uvu ∙ mri ∙ chokidar ∙ zod ∙ @ryanatkn/belt ∙ ESLint ∙ Prettier ∙ svelte-check & more
No vulnerabilities found.
No security vulnerabilities found.