search

InjectiveLabs / injective-helix-demo

Decentralized Derivatives Trading. Any Market. Anytime. Anywhere.
Apache License 2.0
101 stars 74 forks source link

Failed to resolve import "@injectivelabs/token-metadata" from "app/utils/helper.ts". #1025

Open defser opened 4 months ago

defser commented 4 months ago

Failed to resolve import "@injectivelabs/token-metadata" from "app/utils/helper.ts".

injective-helix-demo % yarn dev
yarn run v1.22.21
$ nuxi dev
Nuxt 3.11.2 with Nitro 2.9.6                                                                                                                                                                                           2:04:08 PM

 WARN  The CJS build of Vite's Node API is deprecated. See https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.                                                                2:04:10 PM

                                                                                                                                                                                                                       2:04:10 PM
  ➜ Local:    http://localhost:3000/
  ➜ Network:  use --host to expose

 WARN  The CJS build of Vite's Node API is deprecated. See https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.                                                                2:04:11 PM

 WARN  Ignore Vue I18n configuration file does not exist at i18n.config on layer /Volumes/WORKSPACE/injective-helix-demo/node_modules/.c12/github_InjectiveLabs_injective_1IfPyDVKuA. Skipping...         @nuxtjs/i18n 2:04:11 PM

✔ Nuxt Devtools is enabled v0.7.6 (experimental)                                                                                                                                                                      2:04:11 PM
ℹ Using Tailwind CSS from ~/assets/css/tailwind.css                                                                                                                                                  nuxt:tailwindcss 2:04:12 PM
✔ LCP is optimized for speed                                                                                                                                                                         nuxt-lcp-speedup 2:04:12 PM

ℹ Nuxt collects completely anonymous data about usage.                                                                                                                                                                2:04:12 PM
  This will help us improve Nuxt developer experience over time.
  Read more on https://github.com/nuxt/telemetry

✔ Are you interested in participating?
Yes

ℹ Tailwind Viewer: http://localhost:3000/_tailwind/                                                                                                                                                  nuxt:tailwindcss 2:04:25 PM

 WARN  Using postcss.config.js is not supported together with Nuxt. Use options.postcss instead. You can read more in https://nuxt.com/docs/api/nuxt-config#postcss.                                                   2:04:25 PM

✔ Nuxt Nitro server built in 558 ms                                                                                                                                                                             nitro 2:04:27 PM

 ERROR  Pre-transform error: Failed to resolve import "@injectivelabs/token-metadata" from "app/utils/helper.ts". Does the file exist?                                                                                 2:04:28 PM

ℹ Vite client warmed up in 4030ms

Summary by CodeRabbit

coderabbitai[bot] commented 4 months ago

Walkthrough

This update introduces a single, high-level change: the addition of @injectivelabs/token-metadata version 1.14.11 to the project's package.json dependencies. There are no alterations to the previously exported or public entities in the codebase as part of this update.

Changes

File Change Summary
package.json Added new dependency: @injectivelabs/token-metadata version 1.14.11.

Poem

In our code a new friend dwells,
A token's story it now tells.
With @injectivelabs, so fine,
Our metadata will always shine.
Dependencies grow, the project blooms,
In our code's enchanted rooms.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
socket-security[bot] commented 4 months ago

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@adraffy/ens-normalize@1.10.1 None 0 446 kB adraffy
npm/@injectivelabs/exceptions@1.14.11 Transitive: environment, filesystem, network, shell +7 1.01 MB thomasralee
npm/@injectivelabs/networks@1.14.11 Transitive: environment, filesystem, shell +4 164 kB thomasralee
npm/@injectivelabs/sdk-ts@1.14.13-beta.2 None 0 4.95 MB thomasralee
npm/@injectivelabs/test-utils@1.14.13-beta.0 None 0 33.1 kB thomasralee
npm/@injectivelabs/token-metadata@1.14.11 Transitive: environment, filesystem, shell +8 5.9 MB thomasralee
npm/@injectivelabs/utils@1.14.11 network Transitive: environment, filesystem, shell +6 499 kB thomasralee
npm/@injectivelabs/wallet-ts@1.14.13-beta.3 None 0 1.3 MB thomasralee
npm/bignumber.js@9.1.2 None 0 351 kB mikemcl
npm/google-protobuf@3.21.2 None 0 820 kB dibenede
npm/lodash@4.17.21 None 0 1.41 MB bnjmnt4n
npm/snakecase-keys@5.5.0 None +1 281 kB bendrucker

🚮 Removed packages: npm/@injectivelabs/sdk-ts@1.14.12-beta.5, npm/@injectivelabs/wallet-ts@1.14.12-beta.5, npm/@vue/compiler-dom@3.4.26, npm/@vue/shared@3.4.26, npm/merge2@1.4.1

View full report↗︎

socket-security[bot] commented 4 months ago

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Install scripts npm/@injectivelabs/exceptions@1.14.11
  • Install script: postinstall
  • Source: link-module-alias
 🚫
Install scripts npm/@injectivelabs/networks@1.14.11
  • Install script: postinstall
  • Source: link-module-alias
 🚫
Install scripts npm/@injectivelabs/token-metadata@1.14.11
  • Install script: postinstall
  • Source: link-module-alias
 🚫
Install scripts npm/@injectivelabs/utils@1.14.11
  • Install script: postinstall
  • Source: link-module-alias
 🚫
Install scripts npm/@injectivelabs/test-utils@1.14.13-beta.0
  • Install script: postinstall
  • Source: link-module-alias
 🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/@injectivelabs/exceptions@1.14.11
  • @SocketSecurity ignore npm/@injectivelabs/networks@1.14.11
  • @SocketSecurity ignore npm/@injectivelabs/token-metadata@1.14.11
  • @SocketSecurity ignore npm/@injectivelabs/utils@1.14.11
  • @SocketSecurity ignore npm/@injectivelabs/test-utils@1.14.13-beta.0