Questions tagged [second-generation-packaging]

8 questions with no upvoted or accepted answers
Filter by
Sorted by
Tagged with
4
votes
0answers
37 views

Extending metadata xml without overwriting in org

I'm creating a 2GP managed packaged that adds a custom tab to the Service Console. While developing in a scratch org, the metadata pulled into my project includes a customised version of the Service ...
2
votes
1answer
26 views

Does tests in unlocked packages execute when deploying unpackaged apex code to production?

I'm sorry for the cryptic title. I'm curious what tests are forced to run when deploying to production, if that production org contains unlocked packages. Lets say we have the following test classes ...
2
votes
1answer
44 views

Second gen package error about a component being a scratch org ancestor? What does this mean?

My sfdx-project.json looks like this: { "packageDirectories": [ { "path": "force-app", "package": "my package", ...
2
votes
2answers
22 views

Release new version of unlocked package

I have a sfdx-project.json for my unlocked package. Version 1.0.0-11 was promoted. { "packageDirectories": [ { "path": "force-app", "default": true, "...
2
votes
0answers
53 views

Platform event API name imported in LWC uses “c” instead of “e” as suffix?

I'm trying to make a component in a managed package to subscribe to a certain platform event, and referencing the channel with its API name previously worked: import BATCH_EVENT_NAME from '@...
2
votes
0answers
76 views

Adding a post-install script to a second generation managed package

I'm creating a second gen managed package using sfdx and I'm not sure how to add a post-install script. Most information I've come across involves updating the package from within an org. Is this ...
1
vote
0answers
9 views

sfdx-project.json for second generation package proper ancestry structure?

Currently my sfdx-project.json looks like this: { "packageDirectories": [ { "path": "force-app", "package": "my package&...
1
vote
0answers
19 views

Second Generation Unlocked Packages without Namespace not including components

I'm trying to create a package version for an Unlocked Package with no namespace specified. I can verify this works when running force:package:list and force:package:version:list. I'm including some ...