Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 17 commits into
base: dev
Choose a base branch
from

Conversation

defser
Copy link

@defser defser commented Jun 21, 2024

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

  • Chores
    • Added @injectivelabs/token-metadata as a new dependency to enhance token metadata management.

Copy link

coderabbitai bot commented Jun 21, 2024

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
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • 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 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 for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 27367b8 and a30417d.

Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json

Copy link

socket-security bot commented Jun 21, 2024

🚨 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/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
🚫
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
🚫
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
🚫
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
🚫
Install scripts npm/@injectivelabs/[email protected]
  • 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/[email protected] or ignore all packages with @SocketSecurity ignore-all

Failed to resolve import "@injectivelabs/token-metadata" from "app/utils/helper.ts".
@defser defser force-pushed the fix/failed-to-resolve-@injectivelabs/token-metdata branch from a30417d to 77d9304 Compare June 21, 2024 12:22
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a30417d and 77d9304.

Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • package.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants