Skip to content

Chore: (Docs): Community frameworks location updated - #14849

Merged
shilman merged 1 commit into
nextfrom
adjust_community_frameworks
May 8, 2021
Merged

shilman merged 1 commit into
nextfrom
adjust_community_frameworks

Conversation

@jonniebigodes

Copy link
Copy Markdown
Contributor

With this pull request, the links for the community frameworks such as Rax are updated to their new "home".

Follows up #14796.

Feel free to provide feedback.

@jonniebigodes jonniebigodes added documentation patch:yes Bugfix & documentation PR that need to be picked to main branch labels May 7, 2021
@nx-cloud

nx-cloud Bot commented May 7, 2021 •

Copy link
Copy Markdown

Nx Cloud Report

CI ran the following commands for commit e81051d. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status Command
#000000 nx run-many --target=prepare --all --parallel --max-parallel=15

Sent with 💌 from NxCloud.

...config.plugins,
require.resolve('@babel/plugin-transform-react-jsx')
...config.plugins,
[require.resolve('@babel/plugin-transform-react-jsx'), {}, 'preset'],

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is this change related?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I was checking the changes in the repo for mithril and that caught my eye. Compared it with what's currently documented and updated it accordingly so that we're on the safe side. I can always revert it back

@shilman shilman left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🙌

@shilman
shilman merged commit af6a8d5 into next May 8, 2021
@shilman
shilman deleted the adjust_community_frameworks branch May 8, 2021 12:11
@shilman shilman added the patch:done Patch/release PRs already cherry-picked to main/release branch label May 8, 2021
shilman added a commit that referenced this pull request May 8, 2021
Chore: (Docs): Community frameworks location updated
@yannbf yannbf removed the patch:yes Bugfix & documentation PR that need to be picked to main branch label Oct 28, 2025
@github-actions

Copy link
Copy Markdown
Contributor
Fails
🚫

Danger failed to run .ci/danger/dangerfile.ts.

Error Error

Command failed: npm install lodash
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @storybook/root@6.3.0-alpha.21
npm error Found: eslint@7.32.0
npm error node_modules/eslint
npm error   dev eslint@"^7.17.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^6.0.0" from @storybook/linter-config@2.5.0
npm error node_modules/@storybook/linter-config
npm error   dev @storybook/linter-config@"^2.5.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /github/home/.npm/_logs/2025-10-28T13_44_54_883Z-eresolve-report.txt
npm error A complete log of this run can be found in: /github/home/.npm/_logs/2025-10-28T13_44_54_883Z-debug-0.log

Error: Command failed: npm install lodash
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @storybook/root@6.3.0-alpha.21
npm error Found: eslint@7.32.0
npm error node_modules/eslint
npm error   dev eslint@"^7.17.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^6.0.0" from @storybook/linter-config@2.5.0
npm error node_modules/@storybook/linter-config
npm error   dev @storybook/linter-config@"^2.5.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /github/home/.npm/_logs/2025-10-28T13_44_54_883Z-eresolve-report.txt
npm error A complete log of this run can be found in: /github/home/.npm/_logs/2025-10-28T13_44_54_883Z-debug-0.log

    at genericNodeError (node:internal/errors:984:15)
    at wrappedFn (node:internal/errors:538:14)
    at checkExecSyncError (node:child_process:891:11)
    at execSync (node:child_process:963:15)
    at Object.<anonymous> (.ci/danger/dangerfile.ts:5:30)
    at Module._compile (node:internal/modules/cjs/loader:1521:14)
    at requireFromString (/usr/src/danger/node_modules/require-from-string/index.js:28:4)
    at /usr/src/danger/dist/runner/runners/inline.js:183:68
    at step (/usr/src/danger/dist/runner/runners/inline.js:56:23)
    at Object.next (/usr/src/danger/dist/runner/runners/inline.js:37:53)

Dangerfile

------------------^

Generated by 🚫 dangerJS against e81051d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation patch:done Patch/release PRs already cherry-picked to main/release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants