Kristóf Poduszló

Thanks for reporting! The top-level `README.md` file isn't malfunctioning, but symlinked to [./packages/glaze/README.md](https://github.com/kripod/glaze/blob/master/packages/glaze/README.md), which GitHub shows explicitly [in its per-file view](https://github.com/kripod/glaze/blob/master/README.md). If you wish to clone the repository on Windows,...

That’s the expected behavior, as explained above.

I do care for sure, but the rendering of symlinks is the responsibility of the underlying platform (GitHub in this case, or the OS on developers’ machines). The readme in...

I’ll try my best to revive the issue filed to GitHub above. The `README` displayed belongs to the `glaze` package and needs to be packed along with the `package.json` file...

> As requested, I’ll also try reversing the symlink direction, fixing the issue temporarily. I tried this, but had to conclude that `npm pack` doesn't account for the symlinked readme...

I'm re-opening this issue as [multi-page docs](https://glaze.js.org/) are on the way. Writing new readmes is necessary

@anilanar Thank you for the heads-up! I will work on this once after [adding customizable options for gatsby-plugin-treat](https://github.com/seek-oss/treat/pull/100).

Using [bundlesize](https://github.com/siddharthkp/bundlesize) is partly sufficient. Fuzzy matching may help ignoring files which are not included in the final bundle.

Thank you for the valuable suggestion! Quoting from the [backstory behind treat](https://seek-oss.github.io/treat/background#backstory): > [Linaria](https://linaria.now.sh/) looked a lot more promising due to its theming support, but it came with an important...

I agree, this would be very useful. Currently, I’m working on multi-page docs and then I’ll review #10. Afterwards, the `useStyling()` hook will be re-architectured for improved modularity. I’ll take...