https://netsuiteprofessionals.com logo
Join Slack
Powered by
The problem is the 18.2 tools don’t work in local ...
# suitecommerce
k
The problem is the 18.2 tools don’t work in local dev mode with SC 2019.1, which is why we updated to SCEM 2019.1 in the first place.
c
@Keith Fetterman when I'm trying to run the local environments simultaneously for both extension and themes I'm seeing errors in the console. Did you see the same error?
k
You can’t run extensions and themes at the same time.
😞
c
Previously for 18.2 I have tried to run both. It works fine for me
k
This is based on other posts in the channel from NetSuite.
Personally, I haven’t tried it. I recall a post from a NetSuite developer that it wasn’t supported, but I don’t remember which version they were referring to.
What is the error message?
c
Then we need to deploy the themes everytime?
[231057] Did you forget to signal async completion? events.js:160 throw er; // Unhandled 'error' event ^ Error: listen EADDRINUSE :::7777 at Object.exports._errnoException (util.js102211) at exports._exceptionWithHostPort (util.js104520) at Server._listen2 (net.js126214) at listen (net.js129810) at Server.listen (net.js13769) at Function.listen (D:\Livesites and Demosites\AVT Demo Accounts\Aconcagua - 2019.1 CAP account\SCA 2019.1\ExtensionDevelopmentTools-19.1.0\node_modules\express\lib\application.js61824) at start_server (D:\Livesites and Demosites\AVT Demo Accounts\Aconcagua - 2019.1 CAP account\SCA 2019.1\ExtensionDevelopmentTools-19.1.0\gulp\tasks\connect.js17517) at bound (domain.js28014) at runBound (domain.js29312) at asyncRunner (D:\Livesites and Demosites\AVT Demo Accounts\Aconcagua - 2019.1 CAP account\SCA 2019.1\ExtensionDevelopmentTools-19.1.0\node_modules\async-done\index.js5518) at _combinedTickCallback (internal/process/next_tick.js677) at process._tickDomainCallback (internal/process/next_tick.js1229)
This is the error message
Is there any alternative solution?
k
I think this is the key error message “Error: listen EADDRINUSE :::7777”. It tells me that both servers are using the same port.
c
Is there any solution for this?
k
The alternative is to modify the shopping-local-182.ssp and the gulp/node file that runs the local servers on different ports.
c
Shopping-local-182.ssp?
where can I find this file?
k
If you are familiar with how the shopping-local.ssp and the node files work, it will take a bit of work but it can work
c
Sure @Keith Fetterman I will check this.
k
I just realized that you don’t know what I mean by shopping-local-182.ssp.
Yesterday, with the help of PabloZ, he helped me get 2018.2 local development working with SCEM 2019.1 installed on the server. It required that I build a shopping-local.ssp file using SCA 2018.2, changing the name to shopping-local-182.ssp and uploading it the SuiteCommerce Standard folder in the File Cabinet.
c
Got it. Thanks! After this do you want me to change the ports as well or the above mentioned solution is enough?
k
I don’t know. The shopping-local.ssp from 2018.2 may already take care of this. The issue with only running one at a time may be an SCEM 2019.1 issue. I haven’t tried to run both the local extensions and themes. I do remember when one was port 7778 (I think was themes) and 7779 (extensions?).
But I don’t remember which version of SCA/SC and SCEM was being used.
c
I have changed the ports in the config file in gulp folder.It's working fine @Keith Fetterman
k
Awesome. !!!
I am so glad that NetSuite setup this slack channel.
c
Yes even I feel the same 😊
4 Views
Open in Slack
PreviousNext
Powered by