Is it possible to deploy lightning web components to an org with an api version lower than 45?
I'd like to start developing LWCs in my dev sandbox, but it's current api version is 44. I get this error when trying to deploy my lwc.
Starting SFDX: Deploy Source to Org
19:30:37.961 sfdx force:source:deploy --json --loglevel fatal --sourcepath /Users/tyler/code/salesforce/HelloWorld/force-app/main/default/lwc
{"message":"Deploy failed.","status":1,"stack":"DeployFailed: Deploy failed.n at ALMError (/Users/tyler/.local/share/sfdx/plugins/node_modules/salesforce-alm/dist/lib/almError.js:44:19)n at MetadataRegistry.initializeMetadataTypeInfos.then.catch.e (/Users/tyler/.local/share/sfdx/plugins/node_modules/salesforce-alm/dist/lib/source/sourceApiCommand.js:67:35)n at tryCatcher (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/util.js:16:23)n at Promise._settlePromiseFromHandler (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:510:31)n at Promise._settlePromise (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:567:18)n at Promise._settlePromise0 (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:612:10)n at Promise._settlePromises (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:687:18)n at Async._drainQueue (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:138:16)n at Async._drainQueues (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:148:10)n at Immediate.Async.drainQueues (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:17:14)n at runCallback (timers.js:789:20)n at tryOnImmediate (timers.js:751:5)n at processImmediate [as _immediateCallback] (timers.js:722:5)","name":"DeployFailed","result":[{"error":"Invalid version specified:45.0","type":"","filePath":"N/A"}],"warnings":["All --json output, including on error, is moving to stdout. Use the SFDX_JSON_TO_STDOUT environment variable to move over to the new functionality. This will become the default in version 45."]}
19:30:40.979 sfdx force:source:deploy --json --loglevel fatal --sourcepath /Users/tyler/code/salesforce/HelloWorld/force-app/main/default/lwc ended with exit code 1
Has anyone else been able to successfully deploy a lwc to an org with an api version that is not 45?
lightning-web-components
asked Dec 22 '18 at 3:58
Tyler ZikaTyler Zika
1,0531825
add a comment |
I'd like to start developing LWCs in my dev sandbox, but it's current api version is 44. I get this error when trying to deploy my lwc.
Starting SFDX: Deploy Source to Org
19:30:37.961 sfdx force:source:deploy --json --loglevel fatal --sourcepath /Users/tyler/code/salesforce/HelloWorld/force-app/main/default/lwc
{"message":"Deploy failed.","status":1,"stack":"DeployFailed: Deploy failed.n at ALMError (/Users/tyler/.local/share/sfdx/plugins/node_modules/salesforce-alm/dist/lib/almError.js:44:19)n at MetadataRegistry.initializeMetadataTypeInfos.then.catch.e (/Users/tyler/.local/share/sfdx/plugins/node_modules/salesforce-alm/dist/lib/source/sourceApiCommand.js:67:35)n at tryCatcher (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/util.js:16:23)n at Promise._settlePromiseFromHandler (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:510:31)n at Promise._settlePromise (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:567:18)n at Promise._settlePromise0 (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:612:10)n at Promise._settlePromises (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:687:18)n at Async._drainQueue (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:138:16)n at Async._drainQueues (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:148:10)n at Immediate.Async.drainQueues (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:17:14)n at runCallback (timers.js:789:20)n at tryOnImmediate (timers.js:751:5)n at processImmediate [as _immediateCallback] (timers.js:722:5)","name":"DeployFailed","result":[{"error":"Invalid version specified:45.0","type":"","filePath":"N/A"}],"warnings":["All --json output, including on error, is moving to stdout. Use the SFDX_JSON_TO_STDOUT environment variable to move over to the new functionality. This will become the default in version 45."]}
19:30:40.979 sfdx force:source:deploy --json --loglevel fatal --sourcepath /Users/tyler/code/salesforce/HelloWorld/force-app/main/default/lwc ended with exit code 1
Has anyone else been able to successfully deploy a lwc to an org with an api version that is not 45?
lightning-web-components
asked Dec 22 '18 at 3:58
Tyler ZikaTyler Zika
1,0531825
add a comment |
I'd like to start developing LWCs in my dev sandbox, but it's current api version is 44. I get this error when trying to deploy my lwc.
Starting SFDX: Deploy Source to Org
19:30:37.961 sfdx force:source:deploy --json --loglevel fatal --sourcepath /Users/tyler/code/salesforce/HelloWorld/force-app/main/default/lwc
{"message":"Deploy failed.","status":1,"stack":"DeployFailed: Deploy failed.n at ALMError (/Users/tyler/.local/share/sfdx/plugins/node_modules/salesforce-alm/dist/lib/almError.js:44:19)n at MetadataRegistry.initializeMetadataTypeInfos.then.catch.e (/Users/tyler/.local/share/sfdx/plugins/node_modules/salesforce-alm/dist/lib/source/sourceApiCommand.js:67:35)n at tryCatcher (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/util.js:16:23)n at Promise._settlePromiseFromHandler (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:510:31)n at Promise._settlePromise (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:567:18)n at Promise._settlePromise0 (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:612:10)n at Promise._settlePromises (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:687:18)n at Async._drainQueue (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:138:16)n at Async._drainQueues (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:148:10)n at Immediate.Async.drainQueues (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:17:14)n at runCallback (timers.js:789:20)n at tryOnImmediate (timers.js:751:5)n at processImmediate [as _immediateCallback] (timers.js:722:5)","name":"DeployFailed","result":[{"error":"Invalid version specified:45.0","type":"","filePath":"N/A"}],"warnings":["All --json output, including on error, is moving to stdout. Use the SFDX_JSON_TO_STDOUT environment variable to move over to the new functionality. This will become the default in version 45."]}
19:30:40.979 sfdx force:source:deploy --json --loglevel fatal --sourcepath /Users/tyler/code/salesforce/HelloWorld/force-app/main/default/lwc ended with exit code 1
Has anyone else been able to successfully deploy a lwc to an org with an api version that is not 45?
lightning-web-components
asked Dec 22 '18 at 3:58
Tyler ZikaTyler Zika
1,0531825
I'd like to start developing LWCs in my dev sandbox, but it's current api version is 44. I get this error when trying to deploy my lwc.
Starting SFDX: Deploy Source to Org
19:30:37.961 sfdx force:source:deploy --json --loglevel fatal --sourcepath /Users/tyler/code/salesforce/HelloWorld/force-app/main/default/lwc
{"message":"Deploy failed.","status":1,"stack":"DeployFailed: Deploy failed.n at ALMError (/Users/tyler/.local/share/sfdx/plugins/node_modules/salesforce-alm/dist/lib/almError.js:44:19)n at MetadataRegistry.initializeMetadataTypeInfos.then.catch.e (/Users/tyler/.local/share/sfdx/plugins/node_modules/salesforce-alm/dist/lib/source/sourceApiCommand.js:67:35)n at tryCatcher (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/util.js:16:23)n at Promise._settlePromiseFromHandler (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:510:31)n at Promise._settlePromise (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:567:18)n at Promise._settlePromise0 (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:612:10)n at Promise._settlePromises (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/promise.js:687:18)n at Async._drainQueue (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:138:16)n at Async._drainQueues (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:148:10)n at Immediate.Async.drainQueues (/Users/tyler/.local/share/sfdx/plugins/node_modules/bluebird/js/release/async.js:17:14)n at runCallback (timers.js:789:20)n at tryOnImmediate (timers.js:751:5)n at processImmediate [as _immediateCallback] (timers.js:722:5)","name":"DeployFailed","result":[{"error":"Invalid version specified:45.0","type":"","filePath":"N/A"}],"warnings":["All --json output, including on error, is moving to stdout. Use the SFDX_JSON_TO_STDOUT environment variable to move over to the new functionality. This will become the default in version 45."]}
19:30:40.979 sfdx force:source:deploy --json --loglevel fatal --sourcepath /Users/tyler/code/salesforce/HelloWorld/force-app/main/default/lwc ended with exit code 1
Has anyone else been able to successfully deploy a lwc to an org with an api version that is not 45?
lightning-web-components
lightning-web-components
asked Dec 22 '18 at 3:58
Tyler ZikaTyler Zika
1,0531825
asked Dec 22 '18 at 3:58
Tyler ZikaTyler Zika
1,0531825
asked Dec 22 '18 at 3:58
Tyler ZikaTyler Zika
1,0531825
asked Dec 22 '18 at 3:58
Tyler ZikaTyler Zika
1,0531825
asked Dec 22 '18 at 3:58
Tyler ZikaTyler Zika
1,0531825
1,0531825
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Short answer , you will need pre-release org and API version 45 atleast.
Sign up here for the pre-release org https://www.salesforce.com/form/signup/prerelease-spring19/
You will need pre-release CLI plugin to scaffold the bundle .Install the SFDX CLI (https://developer.salesforce.com/tools/sfdxcli) and then install pre release DX plugin
sfdx plugins:install salesforcedx@pre-release.Install the VScode extension pack for salesforce https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode to get syntax autocomplete , deploy and other language features .
answered Dec 22 '18 at 4:10
Mohith ShrivastavaMohith Shrivastava
60.6k7100142
I'd like to start developing in my dev sandbox now. Do I need to wait till salesforce updates it? How can I get a pre-release org in the mean time?
– Tyler Zika
Dec 22 '18 at 4:11
1
Sign up here salesforce.com/form/signup/prerelease-spring19
– Mohith Shrivastava
Dec 22 '18 at 4:13
3
@TylerZika If you have Sandboxes that will be upgraded, you can do this against your (sandbox copy of) production code too, starting January 4th.
– sfdcfox
Dec 22 '18 at 4:26
I have pre-release dev org, I have 45.0.12 (pre-release) CLI but I'm still getting this issue following Trailhead instructions
– Xtremefaith
2 days ago
I even literally just recreated my org using the link you provided and it still comes back with "sourceApiVersion": "44.0"
– Xtremefaith
2 days ago
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%2f244496%2fis-it-possible-to-deploy-lightning-web-components-to-an-org-with-an-api-version%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Short answer , you will need pre-release org and API version 45 atleast.
Sign up here for the pre-release org https://www.salesforce.com/form/signup/prerelease-spring19/
You will need pre-release CLI plugin to scaffold the bundle .Install the SFDX CLI (https://developer.salesforce.com/tools/sfdxcli) and then install pre release DX plugin
sfdx plugins:install salesforcedx@pre-release.Install the VScode extension pack for salesforce https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode to get syntax autocomplete , deploy and other language features .
answered Dec 22 '18 at 4:10
Mohith ShrivastavaMohith Shrivastava
60.6k7100142
I'd like to start developing in my dev sandbox now. Do I need to wait till salesforce updates it? How can I get a pre-release org in the mean time?
– Tyler Zika
Dec 22 '18 at 4:11
1
Sign up here salesforce.com/form/signup/prerelease-spring19
– Mohith Shrivastava
Dec 22 '18 at 4:13
3
@TylerZika If you have Sandboxes that will be upgraded, you can do this against your (sandbox copy of) production code too, starting January 4th.
– sfdcfox
Dec 22 '18 at 4:26
I have pre-release dev org, I have 45.0.12 (pre-release) CLI but I'm still getting this issue following Trailhead instructions
– Xtremefaith
2 days ago
I even literally just recreated my org using the link you provided and it still comes back with "sourceApiVersion": "44.0"
– Xtremefaith
2 days ago
add a comment |
Short answer , you will need pre-release org and API version 45 atleast.
Sign up here for the pre-release org https://www.salesforce.com/form/signup/prerelease-spring19/
You will need pre-release CLI plugin to scaffold the bundle .Install the SFDX CLI (https://developer.salesforce.com/tools/sfdxcli) and then install pre release DX plugin
sfdx plugins:install salesforcedx@pre-release.Install the VScode extension pack for salesforce https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode to get syntax autocomplete , deploy and other language features .
answered Dec 22 '18 at 4:10
Mohith ShrivastavaMohith Shrivastava
60.6k7100142
I'd like to start developing in my dev sandbox now. Do I need to wait till salesforce updates it? How can I get a pre-release org in the mean time?
– Tyler Zika
Dec 22 '18 at 4:11
1
Sign up here salesforce.com/form/signup/prerelease-spring19
– Mohith Shrivastava
Dec 22 '18 at 4:13
3
@TylerZika If you have Sandboxes that will be upgraded, you can do this against your (sandbox copy of) production code too, starting January 4th.
– sfdcfox
Dec 22 '18 at 4:26
I have pre-release dev org, I have 45.0.12 (pre-release) CLI but I'm still getting this issue following Trailhead instructions
– Xtremefaith
2 days ago
I even literally just recreated my org using the link you provided and it still comes back with "sourceApiVersion": "44.0"
– Xtremefaith
2 days ago
add a comment |
Short answer , you will need pre-release org and API version 45 atleast.
Sign up here for the pre-release org https://www.salesforce.com/form/signup/prerelease-spring19/
You will need pre-release CLI plugin to scaffold the bundle .Install the SFDX CLI (https://developer.salesforce.com/tools/sfdxcli) and then install pre release DX plugin
sfdx plugins:install salesforcedx@pre-release.Install the VScode extension pack for salesforce https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode to get syntax autocomplete , deploy and other language features .
answered Dec 22 '18 at 4:10
Mohith ShrivastavaMohith Shrivastava
60.6k7100142
Short answer , you will need pre-release org and API version 45 atleast.
Sign up here for the pre-release org https://www.salesforce.com/form/signup/prerelease-spring19/
You will need pre-release CLI plugin to scaffold the bundle .Install the SFDX CLI (https://developer.salesforce.com/tools/sfdxcli) and then install pre release DX plugin
sfdx plugins:install salesforcedx@pre-release.Install the VScode extension pack for salesforce https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode to get syntax autocomplete , deploy and other language features .
answered Dec 22 '18 at 4:10
Mohith ShrivastavaMohith Shrivastava
60.6k7100142
edited Dec 22 '18 at 4:27
answered Dec 22 '18 at 4:10
Mohith ShrivastavaMohith Shrivastava
60.6k7100142
answered Dec 22 '18 at 4:10
Mohith ShrivastavaMohith Shrivastava
60.6k7100142
answered Dec 22 '18 at 4:10
Mohith ShrivastavaMohith Shrivastava
60.6k7100142
60.6k7100142
I'd like to start developing in my dev sandbox now. Do I need to wait till salesforce updates it? How can I get a pre-release org in the mean time?
– Tyler Zika
Dec 22 '18 at 4:11
1
Sign up here salesforce.com/form/signup/prerelease-spring19
– Mohith Shrivastava
Dec 22 '18 at 4:13
3
@TylerZika If you have Sandboxes that will be upgraded, you can do this against your (sandbox copy of) production code too, starting January 4th.
– sfdcfox
Dec 22 '18 at 4:26
I have pre-release dev org, I have 45.0.12 (pre-release) CLI but I'm still getting this issue following Trailhead instructions
– Xtremefaith
2 days ago
I even literally just recreated my org using the link you provided and it still comes back with "sourceApiVersion": "44.0"
– Xtremefaith
2 days ago
add a comment |
I'd like to start developing in my dev sandbox now. Do I need to wait till salesforce updates it? How can I get a pre-release org in the mean time?
– Tyler Zika
Dec 22 '18 at 4:11
1
Sign up here salesforce.com/form/signup/prerelease-spring19
– Mohith Shrivastava
Dec 22 '18 at 4:13
3
@TylerZika If you have Sandboxes that will be upgraded, you can do this against your (sandbox copy of) production code too, starting January 4th.
– sfdcfox
Dec 22 '18 at 4:26
I have pre-release dev org, I have 45.0.12 (pre-release) CLI but I'm still getting this issue following Trailhead instructions
– Xtremefaith
2 days ago
I even literally just recreated my org using the link you provided and it still comes back with "sourceApiVersion": "44.0"
– Xtremefaith
2 days ago
I'd like to start developing in my dev sandbox now. Do I need to wait till salesforce updates it? How can I get a pre-release org in the mean time?
– Tyler Zika
Dec 22 '18 at 4:11
I'd like to start developing in my dev sandbox now. Do I need to wait till salesforce updates it? How can I get a pre-release org in the mean time?
– Tyler Zika
Dec 22 '18 at 4:11
1
1
Sign up here salesforce.com/form/signup/prerelease-spring19
– Mohith Shrivastava
Dec 22 '18 at 4:13
Sign up here salesforce.com/form/signup/prerelease-spring19
– Mohith Shrivastava
Dec 22 '18 at 4:13
3
3
@TylerZika If you have Sandboxes that will be upgraded, you can do this against your (sandbox copy of) production code too, starting January 4th.
– sfdcfox
Dec 22 '18 at 4:26
@TylerZika If you have Sandboxes that will be upgraded, you can do this against your (sandbox copy of) production code too, starting January 4th.
– sfdcfox
Dec 22 '18 at 4:26
I have pre-release dev org, I have 45.0.12 (pre-release) CLI but I'm still getting this issue following Trailhead instructions
– Xtremefaith
2 days ago
I have pre-release dev org, I have 45.0.12 (pre-release) CLI but I'm still getting this issue following Trailhead instructions
– Xtremefaith
2 days ago
I even literally just recreated my org using the link you provided and it still comes back with "sourceApiVersion": "44.0"
– Xtremefaith
2 days ago
I even literally just recreated my org using the link you provided and it still comes back with "sourceApiVersion": "44.0"
– Xtremefaith
2 days ago
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%2f244496%2fis-it-possible-to-deploy-lightning-web-components-to-an-org-with-an-api-version%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
