Merged
Conversation
|
Hey, I tried your newest version of next-contextlayer-temp packages only upon building my application it crashes because it searches for 'contentlayer/package.json' file in the check-constraints.js . There is a func called |
Owner
Author
|
@rikvermeulen thanks, good catch - I only tried it out in dev 😄. Updated those lines and it works for |
Owner
Author
|
Changed package name from |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Attempt at publishing a new package:
@contentlayer/*package becomes@contentlayer-temp/*contentlayerrenamed tocontentlayer-tempnext-contentlayerrenamed tonext-contentlayer-temp@contentlayerfolder remains but path alias intsconfig.base.jsonneeds to be updated@contentlayer/source-filesalso need to be updated so the generated code uses the temp packagescontentlayer-temp, dependencies, CLI andcontentlayer.config.tsimports (note: config file name remains the same)All the tests seems to work, with snapshot updated and the examples work fine. To change the package name in the future, search and replace the following phrases:
@contentlayer-tempnext-contentlayer-tempcontentful-generator-tempcontentlayer-stackbit-yaml-generator-tempcontentlayer-tempOther issues:
prepackinnext-contentlayer-tempto useawkinstead ofsed. No idea why thesedcommand was not working for me.mkdirpto use recursive which makes it compatible with memfs 4 if we are upgrading in the future.Published contentlayer-temp and next-contentlayer-temp
v0.4.3and tested that they work usingnext-contentlayer-examplewithout issues on both yarn and npm.