Irae Carvalho
Irae Carvalho
When using wildcards like `/css/*.css` on `.mendelrc`, if a CSS file exists only on a variation and not on `base`, the base bucket for production build is picking up the...
If my variation has a new `require`, Mendel is failing to pick it up right away. If I create a dummy file on my base variation, it starts working again....
I was during my normal developer flow, and I got a git conflict. Git conflicts are pretty common workflow and they often break syntax. Here is what I got back:...
Sometimes, Mendel is resolving files in weird behavior. Although the problem is on my code, it is super hard to track and I only catch this in my CI environment....
Here are the two main use cases: 1. When a new variation is created, mendel-daemon should pickup the new variation. 2. When a variation is deleted, we should stop watching...
During development, sometimes you git pull changes and need to install a new package. I am not proposing Mendel should install the packages, but I think we should track the...
Making a manifest is hard enough, without validation is super hard for someone not familiar with mendel internals. For instance, there is a "outlet" requirement on the "bundle". If you...
`mendel-development` used to be internal library during mendel v1. We need to move forward from this pattern and kill the lib.
In case we detect all mendel modules are `npm link`d in full example, `npm run daemon` should restart when anything inside `packages/*mendel*` changes. This would help a great deal debugging...
Many tests are running against `mendel-browserify` or other deprecated modules. Need to port all tests to `mendel-pipeline` or other appropriate packages, maybe write even more tests.