Marks newer browser destination packages as public packages #3183
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.
This pull request adds a
publishConfig
section to thepackage.json
files for several browser destinations and the browser destination template. This change ensures that these packages are published publicly to the npm registry.Publishing configuration updates:
publishConfig
with"access": "public"
and the npm registry URL topackages/browser-destinations/destinations/evolv-ai/package.json
to enable public publishing.publishConfig
with"access": "public"
and the npm registry URL topackages/browser-destinations/destinations/facebook-conversions-api-web/package.json
to enable public publishing.publishConfig
with"access": "public"
and the npm registry URL to the browser destination template inpackages/cli/templates/destinations/browser/package.json
, ensuring new destinations use the correct publish settings.Testing
Include any additional information about the testing you have completed to
ensure your changes behave as expected. For a speedy review, please check
any of the tasks you completed below during your testing.