fix: fix usage of drizzle when core is used as a dep #283
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Towards #278
Attempting to use
@mapeo/core
as a dep in a separate project breaks because:We don't include the drizzle migration directories when publishing
The path string we provide to drizzle's
migrate()
function is not absolute, which breaks when this is being used as dependency (implementation of how Drizzle attempts to find the migration files based on the provided path is here)I encountered these by using
npm pack
on this repo and then importing as a dep in separate project