Skip to content

What will modules and the package index look like? #13

Closed

Description

@alshdavid

I personally like yaml because the task running steps can be multi line strings, we have comments and everyone knows it.

# project.yaml
scripts:
  start: |
    echo "Hello World"
dependencies:
  main:
    - "git@github.com/foo/bar.git" 
  optional:
    - "git@github.com/foo/bar.git" 
  development:
    - "git@github.com/foo/bar.git" 

Not sure how I will describe dependencies. I quite like Go's use of git to share source, though that would limit packages that prefer to be distributed as private/compiled libraries.

Deno has a cool model too.

Broadly I would like to avoid a central repository like "npm"

Activity

  1. self-assigned this
    on Sep 30, 2021
  2. SuperSonicHub1 commented on Sep 30, 2021

    @SuperSonicHub1
  3. alshdavid commented on Oct 1, 2021

    @alshdavid
    CollaboratorAuthor

    The thing I like about yaml is that it's not foreign to anyone and it will allow for additional configuration to be added for things like the linter or the test runner.

  4. trusktr commented on Oct 1, 2021

    @trusktr

    If you stick with package.json and other similarities, it'll be easier for people to switch.

    AssemblyScript, for example, uses package.json, and node_modules, making it easy for existing TS users to switch to it and using the same tools, VS Codes can provide intellisense using TypeScript and can find dependency types in node_modules like normal, eslint/prettier for formatting, etc.

    If you reinvent all those conventions, it may be a lot more work.

  5. Isaac-Leonard commented on Oct 23, 2021

    @Isaac-Leonard
    Contributor

    I'd prefer using json5 if possible
    YAML has some extremely weird quirks and is best being avoided in my opinion even if it is more readable + its dependent on whitespace which I am not a fan of.
    Perhaps allowing for using both yaml or json5 might be better though.
    On the package repository side a centralised repository like npm would allow for easier adoption I'd imagine, perhaps having a standard repository with a focus on third party repositories and raw git sources might be a good idea?

  6. mindplay-dk commented on Oct 24, 2021

    @mindplay-dk

    I'd prefer using json5 if possible

    Agree. 👍

    Perhaps allowing for using both yaml or json5 might be better though.

    Disagree. 👎

    Having two different package formats is unnecessary complexity.

    The thing I like about yaml is that it's not foreign to anyone and it will allow for additional configuration to be added for things like the linter or the test runner.

    The exact same arguments work for JSON.

    JSON is ubiquitous, universally supported, native to the web - and easy, simple and fast to parse.

  7. Isaac-Leonard commented on Oct 24, 2021

    @Isaac-Leonard
    Contributor

    I agree with everything above but expect push back against not allowing yaml and don't think its really worth trying to convince people otherwise.
    I'd preferably only use json5 for it but some people don't like json and do like yaml so the more people that are happier the better.

  8. locked and limited conversation to collaborators on Feb 17, 2023
  9. converted this issue into a discussion #76 on Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions