michael faith

I'm seeing the same issues with copyright blocks on top of our files. It's removing the blank separator line.

> Default is in `node_modules/@fontsource/plugin-compile/custom.css`. Note that everytime `yarn add`, `npm install` etc, is run, the `custom.css` will be wiped by yarn/NPM if you are using the default output directory...

> Is this documented somewhere ? https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/ https://yarnpkg.com/cli/set/resolution

Why did this go stale? Would love to have this available.

With the announcement of flex-layout's deprecation, would it be possible to prioritize this support? Tailwind is listed as a viable migration route for projects using flex-layout (https://blog.angular.io/modern-css-in-angular-layouts-4a259dca9127). It would be...

> For instance I'm dynamically generating the package version using GitVersion, so if I'd only have that version in the build-directory of my package (which would then not be a...

> > > For instance I'm dynamically generating the package version using GitVersion, so if I'd only have that version in the build-directory of my package (which would then not...

Just to illustrate the point. Let's say I have `packages/pkg-a` and `packages/pkg-b` in my workspace. `pkg-a/package.json` ```json { "name": "pkg-a" "version": "1.0.0" ... } ``` `pkg-b/package.json` ```json { "name": "pkg-b"...

Well, definitely not wrong. I encountered this issue, which is why I'm even here. But I agree, let's keep this issue on task. Happy to discuss with you off-thread.

@CaerusKaru for this and future updates, would it be possible to use peer deps similar to how Angular Material does, which includes the next major version as well, to ease...