Packages going forward #108
-
|
v0.10.0 was released recently. In the release, the Merging @zenfs/port and @zenfs/fetch into @zenfs/coreThe First, they are cross-platform, and one of the reasons why separate packages are used is to prevent pollution of the global namespace with variables that don't actually exist at runtime, which would make working on the project more difficult (e.g. lib.dom). Both @zenfs/fetch and @zenfs/port did not depend on any of these kinds of packages, so that was not a concern. In addition, separate packages help to reduce bundle size. In this case, I don't think that @zenfs/fetch and @zenfs/port add too much to the bundle size: 206KB in 0.9.7 and 217KB in 0.10.0. Packages going forwardI've created this flowchart to describe my process for deciding how to structure the packages: Here are all of the current and planned backends, along with which packages they are or will be part of:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
🚀 1