deno init should add name, version and exports fields to deno.json

[littledivy]

No description provided.

[muddlebee]

@littledivy would like to work on this 👀

[littledivy]

sure!

[muddlebee]

@littledivy

so if I run the command deno init test
something like below should appear in deno.json. correct?

{
  "name" : "test",
  "version": "1.0.0",
  "imports": {},
  "tasks": {
    "dev": "deno run --watch main.ts"
  }
}

but if deno init only then the new fields(name) should be empty?

{
  "name" : "",
  "version": "1.0.0",
  "imports": {},
  "tasks": {
    "dev": "deno run --watch main.ts"
  }
}

deno init docs

[muddlebee]

I am thinking of the approach in codebase, to keep the deno init json template like below and overwrite with the dir option from the deno init <dir> command inside the deno.json {{name}}. original code here

{
  "name" : "{{name}}", 
  "version": "1.0.0",
  "imports": {},
  "tasks": {
    "dev": "deno run --watch main.ts"
  }
}

[littledivy]

Sounds good. This can be the template JSON:

{
  "name": "{{name}}", 
  "version": "0.1.0",
  "exports": {},
  "tasks": {
    "dev": "deno run --watch main.ts"
  }
}

Also note that If dir is not provided it should use the current working directory name.

[dsherret]

Maybe we should only do this when running something like deno init --lib? Not everyone will be developing a library so probably deno init shouldn't do this by default. For example, when adding all three of these fields then someone will get opted into library only lint rules like no-slow-types, which is not necessary for applications.

[bartlomieju]

Maybe we should only do this when running something like deno init --lib? Not everyone will be developing a library so probably deno init shouldn't do this by default. For example, when adding all three of these fields then someone will get opted into library only lint rules like no-slow-types, which is not necessary for applications.

Exactly my thought, +1 for --lib.

[muddlebee]

I have done the changes as per comments above ☝️ and added some unit tests.

[muddlebee]

added some changes to the deno init docs https://github.com/denoland/deno-docs/pull/345/files to reflect the above.