Skip to content

Suggestions #3

Description

@domehead100

Hi Federico,

This was very helpful. Here are a couple of suggestions to limit possible frustration from people trying out your demo who may not be too familiar with the javascript build environment. Typically it is bad practice to install typescript and webpack globally, so users may not have them installed globally (and should not actually).

  • tsc may not be in the command line or may not be a current version. I would add npm install --save-dev typescript so that typescript and tsc are stored within the project. They will be in the ./node_modules/.bin folder. You may want to write a .bat file and/or .sh so that the user can follow your instructions. tsc may be in the path but an old version, e.g., v1 installed by visual studio for .net users
  • webpack may not be in the path or may be an incorrect version stored globally, so a .bat or .sh that launches it might help prevent frustration

Also:

  • your grammar complains about errors from the blank lines between the input, calcs, and outputs sections (I added eol* blocks in between these to get it to stop complaining)

That's about it. Thanks, again very helpful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions