I have been attempting to install SuiteCommerce Ad...
# suitecommerce
k
I have been attempting to install SuiteCommerce Advanced Kilimanjaro source on a new laptop, and I am running into npm install issues. The recommended node version from NetSuite is 6.11.5 and gulp version is 3.9.1. I get an error where the node_modules/.staging directory does not exist. When I look in the node_modules directory, there are no directories. Does anyone have some pointers or suggestions on installing older SCA versions that require the old versions of node and gulp? Here is the error I get:
Copy code
npm ERR! Darwin 23.4.0
npm ERR! argv "/Users/kdf/.nvm/versions/node/v6.11.5/bin/node" "/Users/kdf/.nvm/versions/node/v6.11.5/bin/npm" "install"
npm ERR! node v6.11.5
npm ERR! npm  v3.10.10
npm ERR! path /Users/kdf/tmp/TEST/Kilimanjaro/node_modules/.staging/@types/babylon-754bcab7/package.json
npm ERR! code ENOTDIR
npm ERR! errno -20
npm ERR! syscall open

npm ERR! ENOTDIR: not a directory, open '/Users/kdf/tmp/TEST/Kilimanjaro/node_modules/.staging/@types/babylon-754bcab7/package.json'
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <<https://github.com/npm/npm/issues>>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/kdf/tmp/TEST/Kilimanjaro/npm-debug.log
Is it possible this error is related to MacOS Sonoma 14.4.1 and a filesystem permissions issue?
c
Apple processors and older node versions have problems. It seems that nobody is updating older Node versions to play well with Apple's new M1, M2, M3... processors. You can try running Node as an Intel app: https://www.macworld.com/article/338843/how-to-force-a-native-m1-mac-app-to-run-as-an-intel-app-instead.html
k
Hi @Chris, I ran into a similar problem trying to install node 14.19.0. There was no binary for the M3 and the compiling failed. The following article provided instructions using Rosetta: https://devzilla.io/using-nodejs-14-with-mac-silicon-m
c
Hi Keith... I was just about to post that article. I recently went through this process, and it took me days to figure it out.
Also, for some reason the link posted did not work https://devzilla.io/using-nodejs-14-with-mac-silicon-m1
@Keith Fetterman Have you had any luck fetching or deploying? I have applied the 2 patches and updated 'rest' to 'system' within the ns-deploy/index.js file. Still encountering the following error. https://system.netsuite.com/app/login/secure/authorizetoken.nl?oauth_token=undefined
k
Hi @Christopher Dembek , I think you don’t have all of the patches installed in your SCA Kilimanjaro install. I have also discovered that I can not use the browser based method to obtain the access token. I have to create the token in NetSuite and manually create the token in .nstba. First off, make sure you’ve installed the patches described in following two help articles. Implement them in the order below because the “Enable Token-Based Authentication” was published before the other one. The second help article “Token-Based Authentication Updates for Developer Tools” even says to install the first one first. Enable Token-Based Authentication https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_161109340483.html Token-Based Authentication Updates for Developer Tools https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_9132912150.html Once you’ve done that, I use the following steps to create a token: 1. Log into NetSuite 2. Scroll down the Home dashboard to the “Settings” portlet and click the “Manage Access Tokens” link 3. Create a token 4. Select “SC-TBA” in the “Application Name” field 5. Copy the token and secret 6. Create a new entry in the “.nstba” file in your home folder using the token and secret Fortunately, I was able to use a node_modules folder that already had the patches installed, so all I had to do is create a new access token using the steps above. Good luck.
🙏🏻 1
c
Hi Keith, did you encounter this error? I am on a Mac with the M1 chip.
Copy code
ENOENT: no such file or directory, open 'Kilimanjaro/BB-Chris/SuiteCommerce Advanced Kilimanjaro/ns_npm_repository/suitetalk4node'
k
@Christopher Dembek, I did when I built the downloaded the SCA Kilimanjaro source zip file, but the TBA patches were not applied. I think the error is due to the patches are missing or partially applied. When I worked with the SCA source code with all of the patches applied, I didn’t see the error again.
c
Noted.. thanks for the follow-up!