Skip to content

fix(shared): Fix error on post-build script with existing subpath barel directories#1971

Closed
dimkl wants to merge 1 commit into
mainfrom
fix-shared-postbuild
Closed

fix(shared): Fix error on post-build script with existing subpath barel directories#1971
dimkl wants to merge 1 commit into
mainfrom
fix-shared-postbuild

Conversation

@dimkl

@dimkl dimkl commented Oct 30, 2023

Copy link
Copy Markdown
Contributor

Description

When building a repository with already existing subpath barrel files in shared, the post-build of shared package failed because of trying to create existing subpath files directories.
To resolve this we added a check to only create the directory if it does not exist.

PS: This issue is only visible in local development when the shared package is already built once (after the change that creates temporary directories subpath barrel directories).

Checklist

  • npm test runs as expected.
  • npm run build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Packages affected

  • @clerk/backend
  • @clerk/chrome-extension
  • @clerk/clerk-js
  • @clerk/clerk-expo
  • @clerk/fastify
  • gatsby-plugin-clerk
  • @clerk/localizations
  • @clerk/nextjs
  • @clerk/clerk-react
  • @clerk/remix
  • @clerk/clerk-sdk-node
  • @clerk/shared
  • @clerk/themes
  • @clerk/types
  • build/tooling/chore

@dimkl dimkl self-assigned this Oct 30, 2023
@changeset-bot

changeset-bot Bot commented Oct 30, 2023

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 678a689

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@dimkl
dimkl force-pushed the fix-shared-postbuild branch from 2079ccc to 5af18e9 Compare October 30, 2023 12:17
Comment thread .changeset/mighty-mangos-complain.md Outdated
'@clerk/shared': patch
---

Fix issue with existing directories upon building already built `@clerk/shared`

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is an issue internal to us, I don't think we'd need to put this into the changelog

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.

This issue can be shown in any contributor trying to build the shared package. that's why i have added a changelog entry but i will remove it since you suggest it.

Comment thread scripts/subpath-workaround.mjs Outdated
fs.mkdirSync(new URL(`../packages/${pkgName}/${name}`, import.meta.url));
const directoryURL = new URL(`../packages/${pkgName}/${name}`, import.meta.url);
if (!fs.existsSync(directoryURL)) {
fs.mkdirSync();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

You're missing the directoryURL inside mkdirSync.

For me the function exits early at line 32, did it not do that for you?

@dimkl
dimkl force-pushed the fix-shared-postbuild branch from 5af18e9 to 678a689 Compare October 30, 2023 12:41
@dimkl

dimkl commented Oct 30, 2023

Copy link
Copy Markdown
Contributor Author

Closing in favor of #1974

@dimkl dimkl closed this Oct 30, 2023
@dimkl
dimkl deleted the fix-shared-postbuild branch October 30, 2023 14:56
@clerk-cookie

Copy link
Copy Markdown
Collaborator

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@clerk clerk locked as resolved and limited conversation to collaborators Oct 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants