Diego Fernandez
Diego Fernandez
The problem is in CompileMojo.java:129 : ``` if (output.lastModified() < lessSource.getLastModifiedIncludingImports()) { ``` It should be: ``` if (force || output.lastModified() < lessSource.getLastModifiedIncludingImports()) { ``` But a better solution is...
I still see this issue in `5.3.3` 😞
Note that `pack` is not a script, `npm-run-all pack` is the equivalent of `npm run pack` not `npm pack`
> ... Then basically all changes should be considered breaking. Not all the type changes are breaking: anything that maintains assignment compatibility doesn't make the type-checking fail (adding new optional...
@villasv I agree with you about SemVer. The definition of "breaking change" is vague, and the use of typings wasn't even a use case of Node dependency handling. However, type...
About testing for breaking changes, perhaps we can do something like this: https://github.com/frenic/csstype/blob/master/__tests__/__fixtures__/typecheck.ts#L148 But, with the previous minor version: ```ts import * as PreviousMinor 'previousminor-csstype'; const differentMinorVersions: CSS.Properties = {}...
@FezVrasta I know that API breaking changes are usually not welcome by users, but I'll love to see the changes proposed by @ianstormtaylor When you use `setState` combined with `ref`,...
> I believe @dfernandez79's point is that the current API already has ref-combining issues, so making this change wouldn't actually add a new class of issue to deal with (since...
I didn't have any success on reproducing the issue with smaller cases. I think that React's `forwardRef` definition and the addition of `&` to `Except` may have to do with...
+1 to that :)