-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
init
CLI command
#94
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
init
CLI command with which a new project can be created instead.The
init
command then ask:To keep the command from getting too complex we should concentrate on the most important for now, if there is a need for more configuration options we can always introduce them, so e.g. I would make esbuild to the default bundler and not ask for another.
The
init
command then does the following:npm init
package.json
bypackage.json
(likebuild:types
,build:app
, ..)esbuild
to thedevDependencies
ts-for-gir
to thedevDependencies
(as soon as I have create a new npm package (I think I will name it@ts-for-gir/cli
))tsconfig.json
(with your suggestion to exclude the DOM types)esbuild.js
.ts-for-girrc.js
with the chosenenvironments
:"gjs" | "node"
moduleType
:"esm" | "commonjs"
src/index.ts
as the starting point with a simple exampleOriginally posted by @JumpLink in #72 (comment)
The text was updated successfully, but these errors were encountered: