commercialhaskell / commercialhaskell/stack

Discuss: Should the `stack new` default template still use package.yaml?

Open
#5,778 6 comments 5 reactions 0 assignees View on GitHub
component: init / new type: discuss
Dominant language
Haskell
Stars
4.1k
Forks
850
Avg merge
10h 37m
Merged PRs (30d)
4

Description

### General summary/comments (optional)

Correct me if I am wrong but I think/thought that package.yaml usage is deprecated or no longer recommended with stack - at least that is my understanding. However it seems `stack new` still creates a `package.yaml` file.

### Steps to reproduce

```
$ stack new new-shiny-project
$ ls new-shiny-project
```

### Expected

No `package.yaml` file to be created.

### Actual

`package.yaml` was created.

### Stack version
2.7.5

### Method of installation

* An unofficial package repository: Fedora

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.