imean-sdk - npm Package Compare versions

Comparing version 1.0.0 to 1.1.0

dist/main.js

@@ -10,5 +10,5 @@ function $parcel$defineInteropFlag(a) {
 
-$parcel$export(module.exports, "init", () => $94f3ce79b1f700f4$export$2cd8252107eb640b);
-$parcel$export(module.exports, "default", () => $94f3ce79b1f700f4$export$2e2bcd8739ae039);
-function $57a5ddf50ff9189e$export$2b5b701c862875bb(src, libName) {
+$parcel$export(module.exports, "init", () => $882b6d93070905b3$export$2cd8252107eb640b);
+$parcel$export(module.exports, "default", () => $882b6d93070905b3$export$2e2bcd8739ae039);
+function $3ce58c3d8ee1841e$export$2b5b701c862875bb(src, libName) {
     return new Promise((resolve)=>{
@@ -24,3 +24,3 @@ const dom = document.createElement("script");
 }
-function $57a5ddf50ff9189e$export$49c586b3b863fd35(href) {
+function $3ce58c3d8ee1841e$export$49c586b3b863fd35(href) {
     return new Promise((resolve)=>{
@@ -38,8 +38,8 @@ const dom = document.createElement("link");
 
-async function $94f3ce79b1f700f4$export$2cd8252107eb640b(options) {
+async function $882b6d93070905b3$export$2cd8252107eb640b(options) {
     const { baseUrl: baseUrl = "https://useimean.com"  } = options;
     try {
         await Promise.all([
-            (0, $57a5ddf50ff9189e$export$49c586b3b863fd35)(`${baseUrl}/sdk/main.css`),
-            (0, $57a5ddf50ff9189e$export$2b5b701c862875bb)(`${baseUrl}/sdk/main.js`, "ImeanSDK").then((ImeanSDK)=>{
+            (0, $3ce58c3d8ee1841e$export$49c586b3b863fd35)(`${baseUrl}/sdk/main.css`),
+            (0, $3ce58c3d8ee1841e$export$2b5b701c862875bb)(`${baseUrl}/sdk/main.js`, "ImeanSDK").then((ImeanSDK)=>{
                 try {
@@ -58,5 +58,6 @@ ImeanSDK.init(options);
 }
-var $94f3ce79b1f700f4$export$2e2bcd8739ae039 = $94f3ce79b1f700f4$export$2cd8252107eb640b;
+const $882b6d93070905b3$var$initImeanSdk = $882b6d93070905b3$export$2cd8252107eb640b;
+var $882b6d93070905b3$export$2e2bcd8739ae039 = $882b6d93070905b3$var$initImeanSdk;
 
 
 //# sourceMappingURL=main.js.map

dist/module.js

@@ -1,2 +0,2 @@
-function $b2db502629d273f4$export$2b5b701c862875bb(src, libName) {
+function $09ac412af5115446$export$2b5b701c862875bb(src, libName) {
     return new Promise((resolve)=>{
@@ -12,3 +12,3 @@ const dom = document.createElement("script");
 }
-function $b2db502629d273f4$export$49c586b3b863fd35(href) {
+function $09ac412af5115446$export$49c586b3b863fd35(href) {
     return new Promise((resolve)=>{
@@ -26,8 +26,8 @@ const dom = document.createElement("link");
 
-async function $8cbfd160015d5920$export$2cd8252107eb640b(options) {
+async function $149c1bd638913645$export$2cd8252107eb640b(options) {
     const { baseUrl: baseUrl = "https://useimean.com"  } = options;
     try {
         await Promise.all([
-            (0, $b2db502629d273f4$export$49c586b3b863fd35)(`${baseUrl}/sdk/main.css`),
-            (0, $b2db502629d273f4$export$2b5b701c862875bb)(`${baseUrl}/sdk/main.js`, "ImeanSDK").then((ImeanSDK)=>{
+            (0, $09ac412af5115446$export$49c586b3b863fd35)(`${baseUrl}/sdk/main.css`),
+            (0, $09ac412af5115446$export$2b5b701c862875bb)(`${baseUrl}/sdk/main.js`, "ImeanSDK").then((ImeanSDK)=>{
                 try {
@@ -46,6 +46,7 @@ ImeanSDK.init(options);
 }
-var $8cbfd160015d5920$export$2e2bcd8739ae039 = $8cbfd160015d5920$export$2cd8252107eb640b;
+const $149c1bd638913645$var$initImeanSdk = $149c1bd638913645$export$2cd8252107eb640b;
+var $149c1bd638913645$export$2e2bcd8739ae039 = $149c1bd638913645$var$initImeanSdk;
 
 
-export {$8cbfd160015d5920$export$2cd8252107eb640b as init, $8cbfd160015d5920$export$2e2bcd8739ae039 as default};
+export {$149c1bd638913645$export$2cd8252107eb640b as init, $149c1bd638913645$export$2e2bcd8739ae039 as default};
 //# sourceMappingURL=module.js.map

dist/types.d.ts

@@ -10,5 +10,6 @@ interface InitSdkOptions {
 }
-export default function init(options: InitSdkOptions): Promise<void>;
-export default init;
+export function init(options: InitSdkOptions): Promise<void>;
+declare const initImeanSdk: typeof init;
+export default initImeanSdk;
 
 //# sourceMappingURL=types.d.ts.map

package.json

 {
   "name": "imean-sdk",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "iMean SDK for npm",
@@ -23,5 +23,2 @@ "repository": "https://git.starblazer.cn/imean/imean-sdk-loader.git",
   },
-  "engines": {
-    "node": ">=18"
-  },
   "publishConfig": {
@@ -28,0 +25,0 @@ "access": "public"

README.md

@@ -1,5 +0,7 @@
-# imean-sdk-loader
+# imean-sdk
 
+```ts
+import { init } from 'imean-sdk';
+```
 
-
 ## Getting started
@@ -45,36 +47,46 @@
 
-***
+---
 
 # Editing this README
 
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!).  Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
 
 ## Suggestions for a good README
+
 Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
 
 ## Name
+
 Choose a self-explaining name for your project.
 
 ## Description
+
 Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
 
 ## Badges
+
 On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
 
 ## Visuals
+
 Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
 
 ## Installation
+
 Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
 
 ## Usage
+
 Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
 
 ## Support
+
 Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
 
 ## Roadmap
+
 If you have ideas for releases in the future, it is a good idea to list them in the README.
 
 ## Contributing
+
 State if you are open to contributions and what your requirements are for accepting them.
@@ -87,8 +99,11 @@
 ## Authors and acknowledgment
+
 Show your appreciation to those who have contributed to the project.
 
 ## License
+
 For open source projects, say how it is licensed.
 
 ## Project status
+
 If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

New alerts

AI-detected possible typosquat

Supply chain risk

AI has identified this package as a potential typosquat of a more popular package. This suggests that the package may be intentionally mimicking another package's name, description, or other metadata.

Found 1 instance in 1 package

Fixed alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

17960

increased by1.81%

Lines of code

111

increased by2.78%

Number of lines in readme file

108

increased by16.13%

No dependency changes