Closed barak007 closed 1 year ago
change esbuild peer dependency to >=0.17.18 to allow any future version above @stylable/esbuild original check against version.
>=0.17.18
@stylable/esbuild
Since esbuild itself is in version 0 and breaking changes are allowed in minor, then it's fine have no upper limit.
When esbuild@1 is out we can release a version with an upper limit.
Try clearing the cache for relative package.json to file on rebuild.
package.json
This is a trade off between speed and the need to re-execute the flow when packages are added/removed.
There are other integrations that don't clear this cache and we might want to think of a unified behavior
esbuild: no upper limit on peer-dependency
change esbuild peer dependency to
>=0.17.18to allow any future version above@stylable/esbuildoriginal check against version.Since esbuild itself is in version 0 and breaking changes are allowed in minor, then it's fine have no upper limit.
When esbuild@1 is out we can release a version with an upper limit.
rollup: clear cache
Try clearing the cache for relative
package.jsonto file on rebuild.This is a trade off between speed and the need to re-execute the flow when packages are added/removed.
There are other integrations that don't clear this cache and we might want to think of a unified behavior