Lightning Web Component: A required metadata folder named “lwc” does not exist in this workspace
I am trying to perform this(https://trailhead.salesforce.com/content/learn/projects/quick-start-lightning-web-components/create-a-hello-world-lightning-web-component) with VS code and it is throwing following error.
A required metadata folder named "lwc" does not exist in this workspace.
Performed following steps.
- Installed lightning web component plugin in VS code.
- Created a new SFDX project.
- Error while running SFDX: Create Lightning Web Component.
lightning-web-components
asked Dec 14 '18 at 6:14
Banshi Lal DangiBanshi Lal Dangi
1898
add a comment |
I am trying to perform this(https://trailhead.salesforce.com/content/learn/projects/quick-start-lightning-web-components/create-a-hello-world-lightning-web-component) with VS code and it is throwing following error.
A required metadata folder named "lwc" does not exist in this workspace.
Performed following steps.
- Installed lightning web component plugin in VS code.
- Created a new SFDX project.
- Error while running SFDX: Create Lightning Web Component.
lightning-web-components
asked Dec 14 '18 at 6:14
Banshi Lal DangiBanshi Lal Dangi
1898
Did you signup for pre release org?
– Tushar Sharma
Dec 14 '18 at 6:53
They didn't mention it anywhere, that it will work in spring 19 org only.
– Banshi Lal Dangi
Dec 14 '18 at 10:45
You missed this step in the trailhead where it says you need to create a prerelease org: trailhead.salesforce.com/content/learn/projects/…
– Folkert
Dec 18 '18 at 14:21
add a comment |
I am trying to perform this(https://trailhead.salesforce.com/content/learn/projects/quick-start-lightning-web-components/create-a-hello-world-lightning-web-component) with VS code and it is throwing following error.
A required metadata folder named "lwc" does not exist in this workspace.
Performed following steps.
- Installed lightning web component plugin in VS code.
- Created a new SFDX project.
- Error while running SFDX: Create Lightning Web Component.
lightning-web-components
asked Dec 14 '18 at 6:14
Banshi Lal DangiBanshi Lal Dangi
1898
I am trying to perform this(https://trailhead.salesforce.com/content/learn/projects/quick-start-lightning-web-components/create-a-hello-world-lightning-web-component) with VS code and it is throwing following error.
A required metadata folder named "lwc" does not exist in this workspace.
Performed following steps.
- Installed lightning web component plugin in VS code.
- Created a new SFDX project.
- Error while running SFDX: Create Lightning Web Component.
lightning-web-components
lightning-web-components
asked Dec 14 '18 at 6:14
Banshi Lal DangiBanshi Lal Dangi
1898
asked Dec 14 '18 at 6:14
Banshi Lal DangiBanshi Lal Dangi
1898
asked Dec 14 '18 at 6:14
Banshi Lal DangiBanshi Lal Dangi
1898
asked Dec 14 '18 at 6:14
Banshi Lal DangiBanshi Lal Dangi
1898
asked Dec 14 '18 at 6:14
Banshi Lal DangiBanshi Lal Dangi
1898
1898
Did you signup for pre release org?
– Tushar Sharma
Dec 14 '18 at 6:53
They didn't mention it anywhere, that it will work in spring 19 org only.
– Banshi Lal Dangi
Dec 14 '18 at 10:45
You missed this step in the trailhead where it says you need to create a prerelease org: trailhead.salesforce.com/content/learn/projects/…
– Folkert
Dec 18 '18 at 14:21
add a comment |
Did you signup for pre release org?
– Tushar Sharma
Dec 14 '18 at 6:53
They didn't mention it anywhere, that it will work in spring 19 org only.
– Banshi Lal Dangi
Dec 14 '18 at 10:45
You missed this step in the trailhead where it says you need to create a prerelease org: trailhead.salesforce.com/content/learn/projects/…
– Folkert
Dec 18 '18 at 14:21
Did you signup for pre release org?
– Tushar Sharma
Dec 14 '18 at 6:53
Did you signup for pre release org?
– Tushar Sharma
Dec 14 '18 at 6:53
They didn't mention it anywhere, that it will work in spring 19 org only.
– Banshi Lal Dangi
Dec 14 '18 at 10:45
They didn't mention it anywhere, that it will work in spring 19 org only.
– Banshi Lal Dangi
Dec 14 '18 at 10:45
You missed this step in the trailhead where it says you need to create a prerelease org: trailhead.salesforce.com/content/learn/projects/…
– Folkert
Dec 18 '18 at 14:21
You missed this step in the trailhead where it says you need to create a prerelease org: trailhead.salesforce.com/content/learn/projects/…
– Folkert
Dec 18 '18 at 14:21
add a comment |
2 Answers
2
active
oldest
votes
For now, you need to have the pre-release version installed for DX:
sfdx plugins:install salesforcedx@pre-release
Make sure you've also updated all extensions, including Lightning Web Components, which is not currently part of the Salesforce Extension Pack.
Often, simply restarting after installing/updating all extensions and the pre-release sfdx plugin will automatically create the lwc folder for you. You may also need to close and re-open the folder for it to take effect. I'm not sure how/why my lwc folder appeared, but it wasn't obvious as to what I did.
If all else fails, create a new project in a new, empty directory, and copy the lwc folder back into force-app/main/default/, so that it has two files:
./force-app/main/default/lwc/.eslintrc.json
./force-app/main/default/lwc/jsconfig.json
Once you've done that, you'll stop getting that error and be able to create new components. These config files may require modification if you copy from a new project, so make sure you check the file paths of jsconfig.json. Every time you create a new component with sfdx, jsconfig.json will be updated with more metadata, so make sure you commit this file if you're using a repo.
NOTE: Even though you'll be able to create files locally, to push to the server, you need a pre-release org for now, since all new LWC features are tied to API 45.0 and later, while all production and scratch orgs will be 44.0.
answered Dec 14 '18 at 6:58
sfdcfoxsfdcfox
257k12202445
Thanks. I think the above two files will automatically create when one could create lwc. No need to create them explicitly.
– Anurag Bhardwaj
Dec 31 '18 at 22:55
@AnuragBhardwaj They are supposed to be created, yes, but there was a bug back around when this question was asked (or, at least, it didn't work for me the first time). This is more of a "what happens when things go wrong" answer.
– sfdcfox
Dec 31 '18 at 22:58
add a comment |
You Just need to update the sfdx cli(global) Version :
--> sfdx update
and update all extensions, including Lightning Web Components and Salesforce Extension Pack.
Close the visual code editor,Reopen it and try to create a new project it will automatically create the Lwc folder for you.
answered Dec 17 '18 at 10:36
Chirag KocharChirag Kochar
293
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%2f242580%2flightning-web-component-a-required-metadata-folder-named-lwc-does-not-exist-i%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
For now, you need to have the pre-release version installed for DX:
sfdx plugins:install salesforcedx@pre-release
Make sure you've also updated all extensions, including Lightning Web Components, which is not currently part of the Salesforce Extension Pack.
Often, simply restarting after installing/updating all extensions and the pre-release sfdx plugin will automatically create the lwc folder for you. You may also need to close and re-open the folder for it to take effect. I'm not sure how/why my lwc folder appeared, but it wasn't obvious as to what I did.
If all else fails, create a new project in a new, empty directory, and copy the lwc folder back into force-app/main/default/, so that it has two files:
./force-app/main/default/lwc/.eslintrc.json
./force-app/main/default/lwc/jsconfig.json
Once you've done that, you'll stop getting that error and be able to create new components. These config files may require modification if you copy from a new project, so make sure you check the file paths of jsconfig.json. Every time you create a new component with sfdx, jsconfig.json will be updated with more metadata, so make sure you commit this file if you're using a repo.
NOTE: Even though you'll be able to create files locally, to push to the server, you need a pre-release org for now, since all new LWC features are tied to API 45.0 and later, while all production and scratch orgs will be 44.0.
answered Dec 14 '18 at 6:58
sfdcfoxsfdcfox
257k12202445
Thanks. I think the above two files will automatically create when one could create lwc. No need to create them explicitly.
– Anurag Bhardwaj
Dec 31 '18 at 22:55
@AnuragBhardwaj They are supposed to be created, yes, but there was a bug back around when this question was asked (or, at least, it didn't work for me the first time). This is more of a "what happens when things go wrong" answer.
– sfdcfox
Dec 31 '18 at 22:58
add a comment |
For now, you need to have the pre-release version installed for DX:
sfdx plugins:install salesforcedx@pre-release
Make sure you've also updated all extensions, including Lightning Web Components, which is not currently part of the Salesforce Extension Pack.
Often, simply restarting after installing/updating all extensions and the pre-release sfdx plugin will automatically create the lwc folder for you. You may also need to close and re-open the folder for it to take effect. I'm not sure how/why my lwc folder appeared, but it wasn't obvious as to what I did.
If all else fails, create a new project in a new, empty directory, and copy the lwc folder back into force-app/main/default/, so that it has two files:
./force-app/main/default/lwc/.eslintrc.json
./force-app/main/default/lwc/jsconfig.json
Once you've done that, you'll stop getting that error and be able to create new components. These config files may require modification if you copy from a new project, so make sure you check the file paths of jsconfig.json. Every time you create a new component with sfdx, jsconfig.json will be updated with more metadata, so make sure you commit this file if you're using a repo.
NOTE: Even though you'll be able to create files locally, to push to the server, you need a pre-release org for now, since all new LWC features are tied to API 45.0 and later, while all production and scratch orgs will be 44.0.
answered Dec 14 '18 at 6:58
sfdcfoxsfdcfox
257k12202445
Thanks. I think the above two files will automatically create when one could create lwc. No need to create them explicitly.
– Anurag Bhardwaj
Dec 31 '18 at 22:55
@AnuragBhardwaj They are supposed to be created, yes, but there was a bug back around when this question was asked (or, at least, it didn't work for me the first time). This is more of a "what happens when things go wrong" answer.
– sfdcfox
Dec 31 '18 at 22:58
add a comment |
For now, you need to have the pre-release version installed for DX:
sfdx plugins:install salesforcedx@pre-release
Make sure you've also updated all extensions, including Lightning Web Components, which is not currently part of the Salesforce Extension Pack.
Often, simply restarting after installing/updating all extensions and the pre-release sfdx plugin will automatically create the lwc folder for you. You may also need to close and re-open the folder for it to take effect. I'm not sure how/why my lwc folder appeared, but it wasn't obvious as to what I did.
If all else fails, create a new project in a new, empty directory, and copy the lwc folder back into force-app/main/default/, so that it has two files:
./force-app/main/default/lwc/.eslintrc.json
./force-app/main/default/lwc/jsconfig.json
Once you've done that, you'll stop getting that error and be able to create new components. These config files may require modification if you copy from a new project, so make sure you check the file paths of jsconfig.json. Every time you create a new component with sfdx, jsconfig.json will be updated with more metadata, so make sure you commit this file if you're using a repo.
NOTE: Even though you'll be able to create files locally, to push to the server, you need a pre-release org for now, since all new LWC features are tied to API 45.0 and later, while all production and scratch orgs will be 44.0.
answered Dec 14 '18 at 6:58
sfdcfoxsfdcfox
257k12202445
For now, you need to have the pre-release version installed for DX:
sfdx plugins:install salesforcedx@pre-release
Make sure you've also updated all extensions, including Lightning Web Components, which is not currently part of the Salesforce Extension Pack.
Often, simply restarting after installing/updating all extensions and the pre-release sfdx plugin will automatically create the lwc folder for you. You may also need to close and re-open the folder for it to take effect. I'm not sure how/why my lwc folder appeared, but it wasn't obvious as to what I did.
If all else fails, create a new project in a new, empty directory, and copy the lwc folder back into force-app/main/default/, so that it has two files:
./force-app/main/default/lwc/.eslintrc.json
./force-app/main/default/lwc/jsconfig.json
Once you've done that, you'll stop getting that error and be able to create new components. These config files may require modification if you copy from a new project, so make sure you check the file paths of jsconfig.json. Every time you create a new component with sfdx, jsconfig.json will be updated with more metadata, so make sure you commit this file if you're using a repo.
NOTE: Even though you'll be able to create files locally, to push to the server, you need a pre-release org for now, since all new LWC features are tied to API 45.0 and later, while all production and scratch orgs will be 44.0.
answered Dec 14 '18 at 6:58
sfdcfoxsfdcfox
257k12202445
answered Dec 14 '18 at 6:58
sfdcfoxsfdcfox
257k12202445
answered Dec 14 '18 at 6:58
sfdcfoxsfdcfox
257k12202445
answered Dec 14 '18 at 6:58
sfdcfoxsfdcfox
257k12202445
257k12202445
Thanks. I think the above two files will automatically create when one could create lwc. No need to create them explicitly.
– Anurag Bhardwaj
Dec 31 '18 at 22:55
@AnuragBhardwaj They are supposed to be created, yes, but there was a bug back around when this question was asked (or, at least, it didn't work for me the first time). This is more of a "what happens when things go wrong" answer.
– sfdcfox
Dec 31 '18 at 22:58
add a comment |
Thanks. I think the above two files will automatically create when one could create lwc. No need to create them explicitly.
– Anurag Bhardwaj
Dec 31 '18 at 22:55
@AnuragBhardwaj They are supposed to be created, yes, but there was a bug back around when this question was asked (or, at least, it didn't work for me the first time). This is more of a "what happens when things go wrong" answer.
– sfdcfox
Dec 31 '18 at 22:58
Thanks. I think the above two files will automatically create when one could create lwc. No need to create them explicitly.
– Anurag Bhardwaj
Dec 31 '18 at 22:55
Thanks. I think the above two files will automatically create when one could create lwc. No need to create them explicitly.
– Anurag Bhardwaj
Dec 31 '18 at 22:55
@AnuragBhardwaj They are supposed to be created, yes, but there was a bug back around when this question was asked (or, at least, it didn't work for me the first time). This is more of a "what happens when things go wrong" answer.
– sfdcfox
Dec 31 '18 at 22:58
@AnuragBhardwaj They are supposed to be created, yes, but there was a bug back around when this question was asked (or, at least, it didn't work for me the first time). This is more of a "what happens when things go wrong" answer.
– sfdcfox
Dec 31 '18 at 22:58
add a comment |
You Just need to update the sfdx cli(global) Version :
--> sfdx update
and update all extensions, including Lightning Web Components and Salesforce Extension Pack.
Close the visual code editor,Reopen it and try to create a new project it will automatically create the Lwc folder for you.
answered Dec 17 '18 at 10:36
Chirag KocharChirag Kochar
293
add a comment |
You Just need to update the sfdx cli(global) Version :
--> sfdx update
and update all extensions, including Lightning Web Components and Salesforce Extension Pack.
Close the visual code editor,Reopen it and try to create a new project it will automatically create the Lwc folder for you.
answered Dec 17 '18 at 10:36
Chirag KocharChirag Kochar
293
add a comment |
You Just need to update the sfdx cli(global) Version :
--> sfdx update
and update all extensions, including Lightning Web Components and Salesforce Extension Pack.
Close the visual code editor,Reopen it and try to create a new project it will automatically create the Lwc folder for you.
answered Dec 17 '18 at 10:36
Chirag KocharChirag Kochar
293
You Just need to update the sfdx cli(global) Version :
--> sfdx update
and update all extensions, including Lightning Web Components and Salesforce Extension Pack.
Close the visual code editor,Reopen it and try to create a new project it will automatically create the Lwc folder for you.
answered Dec 17 '18 at 10:36
Chirag KocharChirag Kochar
293
answered Dec 17 '18 at 10:36
Chirag KocharChirag Kochar
293
answered Dec 17 '18 at 10:36
Chirag KocharChirag Kochar
293
answered Dec 17 '18 at 10:36
Chirag KocharChirag Kochar
293
293
add a comment |
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.
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%2f242580%2flightning-web-component-a-required-metadata-folder-named-lwc-does-not-exist-i%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
Did you signup for pre release org?
– Tushar Sharma
Dec 14 '18 at 6:53
They didn't mention it anywhere, that it will work in spring 19 org only.
– Banshi Lal Dangi
Dec 14 '18 at 10:45
You missed this step in the trailhead where it says you need to create a prerelease org: trailhead.salesforce.com/content/learn/projects/…
– Folkert
Dec 18 '18 at 14:21