viqueen / confluence-static-site Goto Github PK

• Upgrading atlaskit components can lead to some unexpected UI changes on the static site
• Setting up a visual regression tests would help capture any issues, so we can automate the dependency upgrades (to some extent of course)

we have a new npm org, let's release this package under @labset scope.

package needs to be public, and the build script needs to run

npm public --access public

see details https://docs.npmjs.com/creating-and-publishing-scoped-public-packages

I successfully used extract space commands to extract space pages and blogs. I've verified this extraction via building and serving the static content later.

However, after blogs are extracted I am getting a long error message that ends with

data: { code: 401, message: 'Unauthorized' }

Other parts of this error message indicate it is related to emojis:

_currentUrl: 'https://admin.atlassian.com/gateway/api/emoji/undefined/site',

I believe it is related to the code on line 19 in this file

To confirm env settings, is there a difference between?
CONFLUENCE_API_TOKEN=
CONFLUENCE_CLOUD_TOKEN=

I am setting both values to my users Atlassian API token. If one is from a different source it might be the culprit here.

I can provide more of error message but it needs to be scrubbed of some session data.

Any thoughts on how to troubleshoot?

Thank you!

Awesome work on the confluence static site generator @viqueen!

I wanted to reach out to see if you would consider adding a license file to the project. This would be consistent with good community practices and would allow others to build upon your work with a clear set of rules for what is permissible.

To ensure maximum compatibility with other software projects, consider the use of the MIT license. Of course, remember to replace the copyright statement with your own copyright information.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• [patch-upgrades] Update all patch dependencies (@atlaskit/breadcrumbs, @atlaskit/date, @atlaskit/link-provider, @atlaskit/media-core, @types/lodash, @types/prompt, @types/react, @types/react-dom, style-loader, ts-node, url, webpack-dev-server)
• [atlaskit-upgrade] Update dependency @atlaskit/page-layout to v1.8.4
• chore(deps): update dependency ts-loader to v9.5.1
• chore(deps): update webdriverio monorepo (@wdio/cli, @wdio/local-runner, @wdio/mocha-framework, @wdio/selenium-standalone-service, @wdio/spec-reporter)
• fix(deps): update dependency css-loader to v6.9.0
• fix(deps): update dependency html-webpack-plugin to v5.6.0
• fix(deps): update dependency sharp to ^0.33.0
• [atlaskit-upgrade] Update atlaskit (major) (@atlaskit/atlassian-navigation, @atlaskit/breadcrumbs, @atlaskit/page-layout, @atlaskit/renderer)
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update actions/upload-artifact action to v4
• chore(deps): update dependency node to v20
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency ubuntu to v22
• chore(deps): update typescript-eslint monorepo to v6 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• fix(deps): update dependency copy-webpack-plugin to v12
• fix(deps): update dependency yet-another-react-lightbox to v3
• 🔐 Create all pending approval PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency eslint to v8.56.0
• chore(deps): update dependency eslint-plugin-import to v2.29.1
• chore(deps): update dependency eslint-plugin-react to v7.33.2
• chore(deps): update dependency typescript to v5.3.3
• chore(deps): update typescript-eslint monorepo to v5.62.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Question for following the steps in Contribution.md:

Question: is npm install --legacy-peer-deps the correct install step for `npm install'?

Details

My steps:

✅ Successfully ran nvm install
❌ Running npm install

Returns error with fix of:

npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution`

Complete error in screenshot

Running

npm install --legacy-peer-deps

does seem to install correctly.

❓ Is this correct way for install to include --legacy-peer-deps?

Steps and Error:

Install with intermediate error: