chore: playground equipment: lint / test dev tools #6
Conversation
$ ../endo/scripts/create-package.sh ag-trade $ mv ../endo/packages/ag-trade/ packages/ create-package.sh: 2024-01-08 15:27 4d7aa98c8 fix(scripts): Update create-package comment doc
- add prettier - ignore node_modules
|
I like the idea of separate lockfiles for various experiments. |
There was a problem hiding this comment.
Don’t trouble to make this perfect.
I don’t feel strongly about whether this should closely resemble the endo repository, but copying scripts and packages/skel along with all the lint configuration you have here certainly makes a lot easier.
Not afraid of a mess in this repo. Maybe someday some stuff graduates to an analogous @endo/kit repo.
There was a problem hiding this comment.
shouldn’t be checked in. maybe need .gitignore.
There was a problem hiding this comment.
do you know how it got there at all?
| @@ -0,0 +1,67 @@ | |||
| { | |||
| "name": "@endo/skel", | |||
There was a problem hiding this comment.
looks like the skeleton unaltered
There was a problem hiding this comment.
yes, this is exactly the skeleton, unaltered; i.e. before we start playing
I'm a little surprised that there are any ag-trade/ files here at all, but I suppose the way I did this was to run the skeleton widget and then try to test / lint and add equipment as needed
factored out of #2
question: should packages such as ag-trade have their own yarn.lock? Or should the whole playground share a yarn.lock?