You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In your comment, you asked for people to be early adopters and I would be happy to be one of them.
How do you envision this package should be used? Ideally, for my own use case, normalized-fs could be set up to replace graceful-fs without much hassle. I see you have a replace-gfs folder in this project - could that be used in other projects?
Perhaps by adding normalized-fs as a (dev) dependency and setting up a resolution for graceful-fs like you have done, it would avoid pulling graceful-fs altogether.
The text was updated successfully, but these errors were encountered:
The replace-gfs package is only used internally atm but I am thinking about moving it out to it's own package that can be used in the way you describe. Would that help?
But yeah, you should be able to override graceful-fs by setting up resolutions to use normalized-fs instead.
Yeah, that could certainly help. Ideally, major projects (like Jest) would drop graceful-fs altogether, but I'm thinking pessimistically — it will take time before it starts disappearing from dependency graphs, so having a standard way of overriding it would be nice for the near term.
In your comment, you asked for people to be early adopters and I would be happy to be one of them.
How do you envision this package should be used? Ideally, for my own use case,
normalized-fs
could be set up to replacegraceful-fs
without much hassle. I see you have areplace-gfs
folder in this project - could that be used in other projects?Perhaps by adding
normalized-fs
as a (dev) dependency and setting up a resolution forgraceful-fs
like you have done, it would avoid pullinggraceful-fs
altogether.The text was updated successfully, but these errors were encountered: