Lightning web components issue with SFDX push and pull
Clash Royale CLAN TAG#URR8PPP
I Create an sfdx scratch org using Quick Start: Lightning Web Components
. I also created a sample hello world lightning web component and pushed it to the scratch org and everything works fine as I was able to preview my hello world lwc in the app builder. I also created an aura component from dev console and was able to pull it to vscode.
Now here comes the issue, Later I created couple of more lwc from the vscode and used push command after saving them, then It shows me what was pushed to the scratch org and everything was fine, but when I actually went to the app builder page of the scratch org that the code was pushed I don't see the newly pushed Lightning web components. Also every time I try to push some deltas I can see the deltas getting pushed.
How do I verify this issue? At least for aura components I can look into lightning resources to see the components but for lwc Im not sure of a way to verify whether they are pushed or not.
Below are the commands used:
sfdx force:source:push // for push
sfdx force:source:pull // for pull
Note: I was able to see the actual lightning web components in the force-app folder in my local host.
PS: From your scratch org
- setup
- Lightning component
- opens a list view where you can see aura components and lwc and I can see all the lwc
Even though all the lightning web components are available in the org,
I was not able to see them in the app builder except for the first
one!
salesforcedx scratch-org lightning-web-components
asked Dec 15 at 20:08
codeyinthecloud
3,194423
add a comment |
I Create an sfdx scratch org using Quick Start: Lightning Web Components
. I also created a sample hello world lightning web component and pushed it to the scratch org and everything works fine as I was able to preview my hello world lwc in the app builder. I also created an aura component from dev console and was able to pull it to vscode.
Now here comes the issue, Later I created couple of more lwc from the vscode and used push command after saving them, then It shows me what was pushed to the scratch org and everything was fine, but when I actually went to the app builder page of the scratch org that the code was pushed I don't see the newly pushed Lightning web components. Also every time I try to push some deltas I can see the deltas getting pushed.
How do I verify this issue? At least for aura components I can look into lightning resources to see the components but for lwc Im not sure of a way to verify whether they are pushed or not.
Below are the commands used:
sfdx force:source:push // for push
sfdx force:source:pull // for pull
Note: I was able to see the actual lightning web components in the force-app folder in my local host.
PS: From your scratch org
- setup
- Lightning component
- opens a list view where you can see aura components and lwc and I can see all the lwc
Even though all the lightning web components are available in the org,
I was not able to see them in the app builder except for the first
one!
salesforcedx scratch-org lightning-web-components
asked Dec 15 at 20:08
codeyinthecloud
3,194423
add a comment |
I Create an sfdx scratch org using Quick Start: Lightning Web Components
. I also created a sample hello world lightning web component and pushed it to the scratch org and everything works fine as I was able to preview my hello world lwc in the app builder. I also created an aura component from dev console and was able to pull it to vscode.
Now here comes the issue, Later I created couple of more lwc from the vscode and used push command after saving them, then It shows me what was pushed to the scratch org and everything was fine, but when I actually went to the app builder page of the scratch org that the code was pushed I don't see the newly pushed Lightning web components. Also every time I try to push some deltas I can see the deltas getting pushed.
How do I verify this issue? At least for aura components I can look into lightning resources to see the components but for lwc Im not sure of a way to verify whether they are pushed or not.
Below are the commands used:
sfdx force:source:push // for push
sfdx force:source:pull // for pull
Note: I was able to see the actual lightning web components in the force-app folder in my local host.
PS: From your scratch org
- setup
- Lightning component
- opens a list view where you can see aura components and lwc and I can see all the lwc
Even though all the lightning web components are available in the org,
I was not able to see them in the app builder except for the first
one!
salesforcedx scratch-org lightning-web-components
asked Dec 15 at 20:08
codeyinthecloud
3,194423
I Create an sfdx scratch org using Quick Start: Lightning Web Components
. I also created a sample hello world lightning web component and pushed it to the scratch org and everything works fine as I was able to preview my hello world lwc in the app builder. I also created an aura component from dev console and was able to pull it to vscode.
Now here comes the issue, Later I created couple of more lwc from the vscode and used push command after saving them, then It shows me what was pushed to the scratch org and everything was fine, but when I actually went to the app builder page of the scratch org that the code was pushed I don't see the newly pushed Lightning web components. Also every time I try to push some deltas I can see the deltas getting pushed.
How do I verify this issue? At least for aura components I can look into lightning resources to see the components but for lwc Im not sure of a way to verify whether they are pushed or not.
Below are the commands used:
sfdx force:source:push // for push
sfdx force:source:pull // for pull
Note: I was able to see the actual lightning web components in the force-app folder in my local host.
PS: From your scratch org
- setup
- Lightning component
- opens a list view where you can see aura components and lwc and I can see all the lwc
Even though all the lightning web components are available in the org,
I was not able to see them in the app builder except for the first
one!
salesforcedx scratch-org lightning-web-components
salesforcedx scratch-org lightning-web-components
asked Dec 15 at 20:08
codeyinthecloud
3,194423
asked Dec 15 at 20:08
codeyinthecloud
3,194423
edited Dec 15 at 20:34
asked Dec 15 at 20:08
codeyinthecloud
3,194423
asked Dec 15 at 20:08
codeyinthecloud
3,194423
asked Dec 15 at 20:08
codeyinthecloud
3,194423
3,194423
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Solved the issue by defining the targets definition in the xml file of the lightning web component.
From the Developer Guide:
There are a few steps to take before you can use your custom Lightning web components to create a Lightning page in Lightning App Builder. One of them is Define Component Metadata in the Configuration File
The .js-meta.xml file defines the metadata values for the component, including the design configuration for components intended for use in Lightning App Builder. Edit the configuration file to:
- Define what types of Lightning pages your component can be used on.
- Configure your component’s properties.
- Set your component’s supported objects.
- Make the component usable outside of your own org.
Added Definition:
<targets>
<target>lightning__RecordPage</target>
<target>lightning__AppPage</target>
<target>lightning__HomePage</target>
</targets>
answered Dec 15 at 20:29
codeyinthecloud
3,194423
add a comment |
There is also another way to see these components , thats using the tooling API query from the dev console .Check the tooling checkbox in the dev console.
The below query should show you if your org has these components
Select Id from LightningComponentBundle
Select Id from LightningComponentResource
The Bundle is the whole bundle and LightningComponentResource are each files.Docs will be out soon then we can get more definitions .
answered Dec 15 at 20:31
Mohith Shrivastava
59.7k795137
+1 Cool. I guess there is still lot of documentation for me to cover! I was missing those targets definition in my xml for the lwc
– codeyinthecloud
Dec 15 at 20:32
There's docs out already, they're in the spring 19 org that go in to a lot of details, including unit testing of these components.
– sfdcfox
Dec 15 at 20:45
1
@sfdcfox not those docs , API docs .Those will be out on Monday
– Mohith Shrivastava
Dec 15 at 20:46
Ah, cool. Thanks for clarifying. Looking forward to it.
– sfdcfox
Dec 15 at 20:46
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "459"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f243722%2flightning-web-components-issue-with-sfdx-push-and-pull%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Solved the issue by defining the targets definition in the xml file of the lightning web component.
From the Developer Guide:
There are a few steps to take before you can use your custom Lightning web components to create a Lightning page in Lightning App Builder. One of them is Define Component Metadata in the Configuration File
The .js-meta.xml file defines the metadata values for the component, including the design configuration for components intended for use in Lightning App Builder. Edit the configuration file to:
- Define what types of Lightning pages your component can be used on.
- Configure your component’s properties.
- Set your component’s supported objects.
- Make the component usable outside of your own org.
Added Definition:
<targets>
<target>lightning__RecordPage</target>
<target>lightning__AppPage</target>
<target>lightning__HomePage</target>
</targets>
answered Dec 15 at 20:29
codeyinthecloud
3,194423
add a comment |
Solved the issue by defining the targets definition in the xml file of the lightning web component.
From the Developer Guide:
There are a few steps to take before you can use your custom Lightning web components to create a Lightning page in Lightning App Builder. One of them is Define Component Metadata in the Configuration File
The .js-meta.xml file defines the metadata values for the component, including the design configuration for components intended for use in Lightning App Builder. Edit the configuration file to:
- Define what types of Lightning pages your component can be used on.
- Configure your component’s properties.
- Set your component’s supported objects.
- Make the component usable outside of your own org.
Added Definition:
<targets>
<target>lightning__RecordPage</target>
<target>lightning__AppPage</target>
<target>lightning__HomePage</target>
</targets>
answered Dec 15 at 20:29
codeyinthecloud
3,194423
add a comment |
Solved the issue by defining the targets definition in the xml file of the lightning web component.
From the Developer Guide:
There are a few steps to take before you can use your custom Lightning web components to create a Lightning page in Lightning App Builder. One of them is Define Component Metadata in the Configuration File
The .js-meta.xml file defines the metadata values for the component, including the design configuration for components intended for use in Lightning App Builder. Edit the configuration file to:
- Define what types of Lightning pages your component can be used on.
- Configure your component’s properties.
- Set your component’s supported objects.
- Make the component usable outside of your own org.
Added Definition:
<targets>
<target>lightning__RecordPage</target>
<target>lightning__AppPage</target>
<target>lightning__HomePage</target>
</targets>
answered Dec 15 at 20:29
codeyinthecloud
3,194423
Solved the issue by defining the targets definition in the xml file of the lightning web component.
From the Developer Guide:
There are a few steps to take before you can use your custom Lightning web components to create a Lightning page in Lightning App Builder. One of them is Define Component Metadata in the Configuration File
The .js-meta.xml file defines the metadata values for the component, including the design configuration for components intended for use in Lightning App Builder. Edit the configuration file to:
- Define what types of Lightning pages your component can be used on.
- Configure your component’s properties.
- Set your component’s supported objects.
- Make the component usable outside of your own org.
Added Definition:
<targets>
<target>lightning__RecordPage</target>
<target>lightning__AppPage</target>
<target>lightning__HomePage</target>
</targets>
answered Dec 15 at 20:29
codeyinthecloud
3,194423
answered Dec 15 at 20:29
codeyinthecloud
3,194423
answered Dec 15 at 20:29
codeyinthecloud
3,194423
answered Dec 15 at 20:29
codeyinthecloud
3,194423
3,194423
add a comment |
add a comment |
There is also another way to see these components , thats using the tooling API query from the dev console .Check the tooling checkbox in the dev console.
The below query should show you if your org has these components
Select Id from LightningComponentBundle
Select Id from LightningComponentResource
The Bundle is the whole bundle and LightningComponentResource are each files.Docs will be out soon then we can get more definitions .
answered Dec 15 at 20:31
Mohith Shrivastava
59.7k795137
+1 Cool. I guess there is still lot of documentation for me to cover! I was missing those targets definition in my xml for the lwc
– codeyinthecloud
Dec 15 at 20:32
There's docs out already, they're in the spring 19 org that go in to a lot of details, including unit testing of these components.
– sfdcfox
Dec 15 at 20:45
1
@sfdcfox not those docs , API docs .Those will be out on Monday
– Mohith Shrivastava
Dec 15 at 20:46
Ah, cool. Thanks for clarifying. Looking forward to it.
– sfdcfox
Dec 15 at 20:46
add a comment |
There is also another way to see these components , thats using the tooling API query from the dev console .Check the tooling checkbox in the dev console.
The below query should show you if your org has these components
Select Id from LightningComponentBundle
Select Id from LightningComponentResource
The Bundle is the whole bundle and LightningComponentResource are each files.Docs will be out soon then we can get more definitions .
answered Dec 15 at 20:31
Mohith Shrivastava
59.7k795137
+1 Cool. I guess there is still lot of documentation for me to cover! I was missing those targets definition in my xml for the lwc
– codeyinthecloud
Dec 15 at 20:32
There's docs out already, they're in the spring 19 org that go in to a lot of details, including unit testing of these components.
– sfdcfox
Dec 15 at 20:45
1
@sfdcfox not those docs , API docs .Those will be out on Monday
– Mohith Shrivastava
Dec 15 at 20:46
Ah, cool. Thanks for clarifying. Looking forward to it.
– sfdcfox
Dec 15 at 20:46
add a comment |
There is also another way to see these components , thats using the tooling API query from the dev console .Check the tooling checkbox in the dev console.
The below query should show you if your org has these components
Select Id from LightningComponentBundle
Select Id from LightningComponentResource
The Bundle is the whole bundle and LightningComponentResource are each files.Docs will be out soon then we can get more definitions .
answered Dec 15 at 20:31
Mohith Shrivastava
59.7k795137
There is also another way to see these components , thats using the tooling API query from the dev console .Check the tooling checkbox in the dev console.
The below query should show you if your org has these components
Select Id from LightningComponentBundle
Select Id from LightningComponentResource
The Bundle is the whole bundle and LightningComponentResource are each files.Docs will be out soon then we can get more definitions .
answered Dec 15 at 20:31
Mohith Shrivastava
59.7k795137
answered Dec 15 at 20:31
Mohith Shrivastava
59.7k795137
answered Dec 15 at 20:31
Mohith Shrivastava
59.7k795137
answered Dec 15 at 20:31
Mohith Shrivastava
59.7k795137
59.7k795137
+1 Cool. I guess there is still lot of documentation for me to cover! I was missing those targets definition in my xml for the lwc
– codeyinthecloud
Dec 15 at 20:32
There's docs out already, they're in the spring 19 org that go in to a lot of details, including unit testing of these components.
– sfdcfox
Dec 15 at 20:45
1
@sfdcfox not those docs , API docs .Those will be out on Monday
– Mohith Shrivastava
Dec 15 at 20:46
Ah, cool. Thanks for clarifying. Looking forward to it.
– sfdcfox
Dec 15 at 20:46
add a comment |
+1 Cool. I guess there is still lot of documentation for me to cover! I was missing those targets definition in my xml for the lwc
– codeyinthecloud
Dec 15 at 20:32
There's docs out already, they're in the spring 19 org that go in to a lot of details, including unit testing of these components.
– sfdcfox
Dec 15 at 20:45
1
@sfdcfox not those docs , API docs .Those will be out on Monday
– Mohith Shrivastava
Dec 15 at 20:46
Ah, cool. Thanks for clarifying. Looking forward to it.
– sfdcfox
Dec 15 at 20:46
+1 Cool. I guess there is still lot of documentation for me to cover! I was missing those targets definition in my xml for the lwc
– codeyinthecloud
Dec 15 at 20:32
+1 Cool. I guess there is still lot of documentation for me to cover! I was missing those targets definition in my xml for the lwc
– codeyinthecloud
Dec 15 at 20:32
There's docs out already, they're in the spring 19 org that go in to a lot of details, including unit testing of these components.
– sfdcfox
Dec 15 at 20:45
There's docs out already, they're in the spring 19 org that go in to a lot of details, including unit testing of these components.
– sfdcfox
Dec 15 at 20:45
1
1
@sfdcfox not those docs , API docs .Those will be out on Monday
– Mohith Shrivastava
Dec 15 at 20:46
@sfdcfox not those docs , API docs .Those will be out on Monday
– Mohith Shrivastava
Dec 15 at 20:46
Ah, cool. Thanks for clarifying. Looking forward to it.
– sfdcfox
Dec 15 at 20:46
Ah, cool. Thanks for clarifying. Looking forward to it.
– sfdcfox
Dec 15 at 20:46
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f243722%2flightning-web-components-issue-with-sfdx-push-and-pull%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown