Frontity Roadmap 
Description
Right now, yarn is not working because yarn doesn’t install local dependencies using symlinks. It copies the folder instead.
Using yarn to install dependencies will cause that npx frontity dev won’t reload automatically an updated version of your project when you change (and save) your code under the packages folder as this problem affects how the modules are linked.
If you have created your project with
npx frontity createor you’re modifying an existing project, you may have some internalscriptsto launch your project.npx run devwon’t work properly as well in most of these cases
When using yarn to install dependencies, the theme you install as a local package, for example…
"dependencies": {
...
"@frontity/mars-theme": "./packages/mars-theme",
...
},
is not linked to your local folder but copied instead. That provokes that changes you do under your packages folder are not detected by the local server that is launched when you do npx frontity dev (and that should reload automatically showing your latest changes when you change your code)
User stories
As a Frontity user
I want to useyarninstead ofnpm,
so that I can keep using the tools I prefer.
Possible solution
We can use symlink-dir at frontity dev.
Workaround
Use npm install instead of yarn.
Doing an npm install won’t work if you have already used yarn before. In that case, you must delete the node_modules folder and use npm install again.