Skip to content
This repository was archived by the owner on Jul 6, 2025. It is now read-only.
This repository was archived by the owner on Jul 6, 2025. It is now read-only.

Necessity of VSCode-specific files #46

Closed
@italodeandra

Description

@italodeandra

Off-topic

Hi guys, first of all congratulations on the library it seems really promising. It actually got me into deno again, I'll be trying it in some hobby projects and maybe in the future contribute for it to get production-ready.

This "issue" is actually a discussion, but as the discussion feature is not available I think it might not be bad submitting an issue, you guys can close and suggest me a better place if I'm wrong.

Necessity of VSCode-specific files

I would like to understand the necessity of the library adding VSCode-specific files when using the CLI init command. This is the first template that I see doing it and think it was really unnecessary but I still would like to understand better the necessity of it.

My suggestion would be either making it an optional flag or using --template like CRA.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions