CyberSource / CyberSource/cybersource-rest-samples-node

Can't resolve 'ApiClient'

Open
#72 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
43
Forks
66
Avg merge
23m
Merged PRs (30d)
2

Description

Using the package with Next 13 causing this issue:

`Did you mean './ApiClient'?
Requests that should resolve in the current directory need to start with './'.
Requests that start with a name are treated as module requests and resolve within module directories (node_modules, /Users/codeclouds-sourabh/Documents/essex/node_modules/.pnpm/next@13.4.8_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/bin/node_modules, /Users/codeclouds-sourabh/Documents/essex/node_modules/.pnpm/next@13.4.8_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/node_modules, /Users/codeclouds-sourabh/Documents/essex/node_modules/.pnpm/next@13.4.8_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0/node_modules/next/node_modules, /Users/codeclouds-sourabh/Documents/essex/node_modules/.pnpm/next@13.4.8_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0/node_modules, /Users/codeclouds-sourabh/Documents/essex/node_modules/.pnpm/node_modules, /Users/codeclouds-sourabh/Documents/essex).
If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./app/api/revalidate/route.ts

  • warn Fast Refresh had to perform a full reload due to a runtime error.`

Code Snippet

import * as cybersourceRestApi from 'cybersource-rest-client';
var instance = new cybersourceRestApi.KeyGenerationApi({ authenticationType: 'http_signature', runEnvironment: 'cybersource.environment.SANDBOX', merchantID, merchantKeyId, merchantsecretKey, keyAlias: 'testrest', keyPass: 'testrest', keyFileName: 'testrest', keysDirectory: 'Resource', enableLog: true, logFilename: 'cybs', logDirectory: '../log', logFileMaxSize: '5242880' }); var request = new cybersourceRestApi.GeneratePublicKeyRequest(); request.encryptionType = 'RsaOaep256'; request.targetOrigin = 'http://localhost:3000'; var opts: { format: any } = { format: 'jwt' }; instance.generatePublicKey(request, opts, function (error: any, data: any, response: any) { if (error) { console.log('Error : ' + error); console.log('Error status code : ' + error.statusCode); } else if (data) { console.log('Data : ' + JSON.stringify(data)); console.log('CaptureContext: ' + data.keyId); } console.log('Response : ' + JSON.stringify(response)); console.log('Response Code Of GenerateKey : ' + response['status']); console.error(error, data); }); }

Do you have any idea how to resolve this issue? Have tried altering the webpack config using next.config.js and that didn't fix anything. Any help is appreciated.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the module-not-found error from app/api/revalidate/route.ts with Next 13, then inspect next.config.js and the cybersource-rest-client import. Done means the API route builds and runs without the 'ApiClient' resolution error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, next.js
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.