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

Unable to build, mermaid package not found #1

Closed
Hydragyrum opened this issue Nov 26, 2019 · 3 comments
Closed

Unable to build, mermaid package not found #1

Hydragyrum opened this issue Nov 26, 2019 · 3 comments

Comments

@Hydragyrum
Copy link

Hydragyrum commented Nov 26, 2019

I am unable to perform a yarn install of this repo, as the @mermaid-js/mermaid seems to not exist on the yarn package repo.

Console log as follows:

yarn install v1.19.2
info No lockfile found.
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files.
 To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
warning jsonlint > [email protected]: Package no longer supported. Contact [email protected] for more info.
error An unexpected error occurred: "https://registry.yarnpkg.com/@mermaid-js%2fmermaid: Not found".
info If you think this is a bug, please open a bug report with the information provided in "/<snip>/mermaid-live-editor/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
@Hydragyrum
Copy link
Author

Hydragyrum commented Nov 26, 2019

error log follows:

Arguments:
  /home/<USER>/.nvm/versions/node/v12.13.1/bin/node /<YARN_PATH>/yarn/bin/yarn.js install

PATH:
  <Removed for confidentiality reasons>

Yarn version:
  1.19.2

Node version:
  12.13.1

Platform:
  linux x64

Trace:
  Error: https://registry.yarnpkg.com/@mermaid-js%2fmermaid: Not found
      at Request.params.callback [as _callback] (/<NODE_PATH>/nodejs/v12.13.1/node_modules/yarn/lib/cli.js:66927:18)
      at Request.self.callback (/<NODE_PATH>/v12.13.1/node_modules/yarn/lib/cli.js:140586:22)
      at Request.emit (events.js:210:5)
      at Request.<anonymous> (/<NODE_PATH>/v12.13.1/node_modules/yarn/lib/cli.js:141558:10)
      at Request.emit (events.js:210:5)
      at IncomingMessage.<anonymous> (/<NODE_PATH>/v12.13.1/node_modules/yarn/lib/cli.js:141480:12)
      at Object.onceWrapper (events.js:299:28)
      at IncomingMessage.emit (events.js:215:7)
      at endReadableNT (_stream_readable.js:1184:12)
      at processTicksAndRejections (internal/process/task_queues.js:80:21)

npm manifest:
  {
    "name": "mermaid-live-editor",
    "version": "1.0.0",
    "license": "MIT",
    "devDependencies": {
      "cross-env": "^5.2.0",
      "css-loader": "^2.1.1",
      "mini-css-extract-plugin": "^0.6.0",
      "serve": "^11.0.0",
      "style-loader": "^0.23.1",
      "svelte": "^3.0.0",
      "svelte-loader": "2.13.3",
      "webpack": "^4.30.0",
      "webpack-cli": "^3.3.0",
      "webpack-dev-server": "^3.3.1"
    },
    "scripts": {
      "build": "cross-env NODE_ENV=production webpack",
      "dev": "webpack-dev-server --content-base docs"
    },
    "dependencies": {
      "js-base64": "^2.5.1",
      "json-lint": "^0.1.0",
      "jsonlint": "^1.6.3",
      "@mermaid-js/mermaid": "8.4.3-preview.795",
      "moment": "^2.24.0",
      "monaco-editor": "0.18.1",
      "svelte-routing": "^1.4.0",
      "svelte-spa-router": "^1.3.0"
    }
  }

yarn manifest:
  No manifest

Lockfile:
  No lockfile

@knsv
Copy link
Contributor

knsv commented Dec 7, 2019

Hi!
Try now. At that moment the repo was using an preview version of mermaid from the github package respository. You could setup npm/yarn to use that.

Now after the release it is again using the standard package.

I will add a markdown file explaining how to do this. I will have the preview version at a different path in the future. This has been my forst experiment with sveltejs and I am quite happy with svelte. The stores could probably be setup differently if this was a bigger app but for this purpose it works.

@knsv
Copy link
Contributor

knsv commented Jan 22, 2020

The github package @mermaid-js/mermaid is now relegated to the develop branch for the preview versions of mermaid so this should no longer be an issue.
Thanks for you report.

@knsv knsv closed this as completed Jan 22, 2020
knsv pushed a commit that referenced this issue Jun 1, 2021
sidharthv96 pushed a commit that referenced this issue Sep 14, 2021
sidharthv96 pushed a commit that referenced this issue Nov 9, 2023
fix: interface SVG was changed by mistake
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

No branches or pull requests

2 participants