From Discord: Request for New Release of @effect/schema with Re-export and Peer Dependency Declaration

[effect-bot]

Summary

User requests a new release of the @effect/schema package that simply re-exports effect/schema and declares the effect package as a peer dependency. This change is intended to resolve ongoing issues related to dependency conflicts, referred to as "LLM fuckery" in the conversation.

Discord thread

https://discord.com/channels/795981131316985866/1472837829011968145

[mikearnaldi]

We won't be accepting this suggestion, the thought process is that packages will inevitably change over time and the user should not assume AI is perfect by default with them, in this case the solution is to write "the package @effect/schema is deprecated, all the modules are now in effect/Schema" in whatever agent config you use (i.e. AGENTS.md). Also good practice to add lint rules to prevent future usage, i.e. ask the model to "please write a local lint rule to ban usage of @effect/schema".

In 4.0 there will be many changes and very much likely AI will get confused for a while, we will try to provide context files to make it better but it's inevitable (i.e. the only safe bet is to assume AI has general knowledge and specific knowledge is up to user to design in context)