move @inlang/core/fs
back to @inlang/core/config
#440
Replies: 3 comments 5 replies
-
Or, we could move environment functions out of |
Beta Was this translation helpful? Give feedback.
5 replies
-
sounds reasonable as it is no implementation of an FS and just types |
Beta Was this translation helpful? Give feedback.
0 replies
-
closed in #471 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Problem
@openscript as part of https://github.com/orgs/inlang/discussions/373, we moved
fs
into its own directory and defined exports for@inlang/core/fs
.I remember now why I used
typeof fs
, I don't expect@inlang/core
to contain an implementation offs
.@inlang/core
defines the API for an environment function$fs
. The underlying implementation is external e.g. node, vscode, or a browser implementation. The browser implementation we will likely develop as part of@inlang/git-sdk
or@inlang/fs
but not core itself.Proposal
Move
fs
back toconfig
and prefix it with$
again to signal this is an environment function that is passed to the "environment" and implemented externally.Beta Was this translation helpful? Give feedback.
All reactions