Removing the need for a package json #1261
Open
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.
The lib requires the consumer to have a valid
package.json
present in the project since the styles are scoped based on the package'sname
.There are cases where a
package.json
does not exist in a project, for example, tools like Bit.dev don't have (always) available a package.json file (since they are managed internally), making Vanilla Extract unusable.This proposal allows the user to provide a
packageName
, which is optional, and defaults to the current behavior.Alternatives:
scopeName
packageJson
options (which can be an object and/or a function that returns an object) where the user can provide a valid package json object. This would be helpful if in the future some other properties of the package json are needed