celitech-sdk 2.0.7 → 2.0.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "celitech-sdk",
3
- "version": "2.0.7",
4
- "description": "Welcome to the CELITECH API documentation! Useful links: [Homepage](https://www.celitech.com) | [Support email](mailto:support@celitech.com) | [Blog](https://www.celitech.com/blog/)",
3
+ "version": "2.0.10",
4
+ "description": "Welcome to the CELITECH API documentation! Useful links: [Homepage](https://www.celitech.com) | [Support email](mailto:devops@celitech.com) | [Blog](https://www.celitech.com/blog/) # Introduction This is the reference documentation and schemas for the CELITECH API and webhooks. For tutorials and other documentation please refer to the [CELITECH Documentation](https://docs.celitech.com). \"Partners\" refers to online service providers that use our eSIM API. Access levels include Gold, Platinum, and Diamond. ## API The CELITECH API is designed for use by partner platforms, including both web and mobile applications. It's assumed all endpoint calls are initiated from the backend of an integrated platform. API URL: `https://api.celitech.net/v1` ## Authentication & Authorization CELITECH API uses the OAuth 2.0 protocol for authentication and authorization. The endpoints are protected using client credentials flow which is based on a token exchange. The token has a defined life span (typically 1 hour), after which a new token must be obtained. To begin, obtain OAuth 2.0 client credentials ( **CLIENT_ID** & **CLIENT_SECRET** ) from the [CELITECH Dashboard](https://www.dashboard.celitech.com/). Then your client application requests an access token from the CELITECH Authorization Server, extracts a token from the response, and sends the token to the CELITECH API that you want to access. Security Scheme Type: `OAuth2` Flow type: `clientCredentials` Token URL: `https://auth.celitech.net/oauth2/token`",
5
5
  "source": "./src/index.ts",
6
6
  "main": "./dist/index.js",
7
7
  "module": "./dist/index.mjs",
@@ -10,7 +10,7 @@
10
10
  "types": "./dist/index.d.ts",
11
11
  "scripts": {
12
12
  "test": "tsc --noEmit",
13
- "build": "tsup-node src/index.ts --format cjs,esm --dts --clean",
13
+ "build": "tsup-node src/index.ts --format cjs,esm --dts --clean && node -e \"const fs=require('fs');const path=require('path');function fx(s,d){const dir=path.dirname(s);const c=fs.readFileSync(s,'utf8');const p=c.replace(/((?:from|import)\\s*\\(?\\s*[\\x27\\x22])(\\.\\.?\\/[^\\x27\\x22]+?)([\\x27\\x22])/g,(m,a,b,e)=>{if(/\\.[a-zA-Z0-9]+$/.test(b))return m;const suffix=fs.existsSync(path.join(dir,b)+'.d.ts')?'.js':'/index.js';return a+b+suffix+e});fs.writeFileSync(d,p)};fx('dist/index.d.ts','dist/index.d.mts')\"",
14
14
  "prepublishOnly": "chmod +x ./scripts/prepublish.sh && ./scripts/prepublish.sh && npm run build",
15
15
  "test-example": "cd examples && tsc --noEmit"
16
16
  },
@@ -38,11 +38,22 @@
38
38
  "dependencies": {
39
39
  "zod": "3.22.3"
40
40
  },
41
+ "engines": {
42
+ "node": ">=18.0.0"
43
+ },
44
+ "sideEffects": false,
41
45
  "exports": {
42
46
  ".": {
43
- "require": "./dist/index.js",
44
- "import": "./dist/index.mjs",
45
- "types": "./dist/index.d.ts"
46
- }
47
+ "require": {
48
+ "types": "./dist/index.d.ts",
49
+ "default": "./dist/index.js"
50
+ },
51
+ "import": {
52
+ "types": "./dist/index.d.mts",
53
+ "default": "./dist/index.mjs"
54
+ },
55
+ "default": "./dist/index.js"
56
+ },
57
+ "./package.json": "./package.json"
47
58
  }
48
59
  }