feat: TUP-700 @tacc/core-components - publish #464
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5 tasks
To avoid error like: ``` npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: hazmapper@0.0.0 npm ERR! Found: vite@3.2.10 npm ERR! node_modules/vite npm ERR! dev vite@"^3.0.7" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer vite@"^5.0.0" from @nx/vite@17.3.2 npm ERR! node_modules/@nx/vite npm ERR! peer @nx/vite@"^17.2.8" from @tacc/core-components@0.0.1 npm ERR! node_modules/@tacc/core-components npm ERR! @tacc/core-components@"file:../../tacc-core-components-0.0.1.tgz" from the root project ```
wesleyboar
changed the base branch from
main
to
epic/TUP-700-core-components-node-pkg
5 tasks
wesleyboar
force-pushed
the
feat/TUP-700-core-components-node-pkg--publish
branch
from
8932544
to
cc60342
Compare
…0-core-components-node-pkg--publish
…0-core-components-node-pkg--publish
The commands via `nx` for core-components DO work!
wesleyboar
merged commit 41116e6
into
epic/TUP-700-core-components-node-pkg
1 check passed
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Publish @tacc/core-components.
Status
Tip
Ready to publish as of 516b344 (or merge commit 41116e6)!
Important
Unable to publish, because repository is private. 🫤
Related
Changes
vite-plugin-lib-inject-cssversionTesting
Package
@tacc/core-componentsrm -rf node_modulesnpm install --include=optional --workspace=libs/core-componentsBuild
@tacc/core-componentsi.e.npx nx build core-components --skip-nx-cachePackage
@tacc/core-components(for use in local install) e.g.npm pack --workspace=libs/core-components --pack-destination=../1Prepare a client to use
@tacc/core-componentspackage.I did this in feat: tup-700 @tacc/core-components node pkg TACC-Cloud/hazmapper#239.
react/src/core-componentsandreact/src/core-wrappers.core-componentsandcore-wrappers.imports ofcore-componentsandcore-wrapperswith@tacc/core-components.importreferences tocore-componentsandcore-wrappers.Set up https://github.com/TACC-Cloud/hazmapper.
Verify app renders with its core-components.
Checkout
feat/TUP-700-core-components-node-pkg--use-pkg.npm install --save ../../tacc-core-components-0.0.1.tgz1npm ciVerify no errors from previous steps.2
Publish
@tacc/core-componentsnpx nx build core-components --skip-nx-cachenpm publish --dry-run --workspace=libs/core-componentsUI
Build
@tacc/core-components(via NX)Publish
@tacc/core-components("Dry Run")Notes
Warning
npm WARN publish Removed invalid "scripts", see [BUG] Unwxpwcted warning "Removed invalid scripts" on publish npm/cli#6918 (comment).Footnotes
Tester should check paths to
@tacc/core-components: to where to package, from where to install. ↩ ↩2Warnings are expected. See "Notes". ↩ ↩2