Conversation
Co-authored-by: Mokshit Jain <mokshitjain2006@gmail.com>
|
|
Is this missing a changeset? Or are you planning to publish in a follow-up PR? |
Co-authored-by: Mark Dalgleish <mark.john.dalgleish@gmail.com>
|
Packages are auto published if they haven't been published before. So you don't need a changeset for the first release. |
| }; | ||
| } | ||
|
|
||
| const stringifyExports = (value: any) => |
There was a problem hiding this comment.
More just marking this for future conversation, but this makes me think it might be good to have a more first-class integration API so stuff like this is handled for you.
markdalgleish
left a comment
There was a problem hiding this comment.
A few comments, but nothing to hold up an approval. This is super exciting 🔥
Current limitations:
projectRootplugin option must be set to get deterministic class name hashes between build systemsIf
projectRootisn't set, fileScope will fallback to absolute paths. This is fine when building locally, but causes hash differences across different machines which would break caching.