update package name #2
Merged
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/*
contentlayer
renamed tocontentlayer-temp
next-contentlayer
renamed tonext-contentlayer-temp
@contentlayer
folder remains but path alias intsconfig.base.json
needs to be updated@contentlayer/source-files
also need to be updated so the generated code uses the temp packagescontentlayer-temp
, dependencies, CLI andcontentlayer.config.ts
imports (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-temp
next-contentlayer-temp
contentful-generator-temp
contentlayer-stackbit-yaml-generator-temp
contentlayer-temp
Other issues:
prepack
innext-contentlayer-temp
to useawk
instead ofsed
. No idea why thesed
command was not working for me.mkdirp
to 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.3
and tested that they work usingnext-contentlayer-example
without issues on both yarn and npm.