Closed timlrx closed 5 months ago
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 checkContentlayerVersionsMatch
that checks the package.json, only it tries to check the file from original package. These two lines need to be updated to 'contentlayer-temp' and 'next-contentlayer-temp'
const contentlayerVersion = getPackageVersion('contentlayer');
const nextContentlayerVersion = getPackageVersion('next-contentlayer');
@rikvermeulen thanks, good catch - I only tried it out in dev 😄. Updated those lines and it works for next build
as well! Released as v0.4.4
Changed package name from contentlayer-temp
to contentlayer2
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.