# Suggestion for a new package: MinimalWorkingExamples.jl

**URL:** <https://discourse.julialang.org/t/suggestion-for-a-new-package-minimalworkingexamples-jl/59391>\
**Category:** Package Announcements\
**Tags:** question, package\
**Created:** [April 16, 2021, 7:43am UTC](https://discourse.julialang.org/t/suggestion-for-a-new-package-minimalworkingexamples-jl/59391 "2021-04-16T07:43:27Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [April 16, 2021, 3:36pm UTC](https://discourse.julialang.org/t/suggestion-for-a-new-package-minimalworkingexamples-jl/59391/23 "2021-04-16T15:36:36Z")

</div>

This example underscores my point above: you really need a manifest for anything nontrivial. Note how the [code in that example](https://discourse.julialang.org/t/concatenate-csv-data-into-feather-using-datastreams/3690/) is outdated now (will fail at `CSV.Source`).

I think it would be better to come up with a convenience solution that reproduces an environment in a few steps, rather than just automatically downloading the latest versions of some packages. And, from the user side, that packs code + manifest to an archive or a gist.

---

_[View the full topic](https://discourse.julialang.org/t/suggestion-for-a-new-package-minimalworkingexamples-jl/59391)._