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.

Sign up for GitHub

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

Jump to bottom

Changed output directory structure in 0.2.2 #281

Closed
GNURub opened this issue Jan 24, 2024 · 9 comments · Fixed by #283
Closed

Changed output directory structure in 0.2.2 #281

GNURub opened this issue Jan 24, 2024 · 9 comments · Fixed by #283

Comments

@GNURub
Copy link

GNURub commented Jan 24, 2024

breaking changes

Configurations with "paths" alias generates a diferent output directory:

  • v0.2.0 -> dist/
  • v0.2.2 -> dist/src/
@kdy1
Copy link
Member

kdy1 commented Jan 24, 2024

f87c850 reverts the changes in v0.2.2

@kdy1 kdy1 closed this as completed Jan 24, 2024
@ShogunPanda
Copy link
Contributor

This was then reintroduced in v0.3.0.
Is there a way to get v0.2.x behavior in the latest version?

@kdy1
Copy link
Member

kdy1 commented Jan 24, 2024

You can use v0.2.3, but not inv0.3.x

@ShogunPanda
Copy link
Contributor

Sorry, I'll rephrase: is there any option (or plan to add an option) in v0.3.x to get the same behavior?
If not, would you accept a PR for it?

@kdy1 kdy1 mentioned this issue Jan 25, 2024
Closed
@kdy1
Copy link
Member

kdy1 commented Jan 25, 2024

I'll accept a PR, but I'm not sure about the name of the option

@ShogunPanda
Copy link
Contributor

Let's choose it together. Out of my mind I'm thinking about the following (in order of preference):

  1. --strip-leading-paths
  2. --resolve-destination-paths
  3. --strip-leading-destination-paths

Do you like any of those? Or do you have any similar suggestion?

@kdy1
Copy link
Member

kdy1 commented Jan 25, 2024

I also prefer the first one

@lpgera lpgera mentioned this issue Jan 25, 2024
Closed
lpgera added a commit to lpgera/dirigera-web that referenced this issue Jan 25, 2024
@lpgera
pin @swc/cli to 0.2.3
1f7d41e 
swc-project/cli#281
@kdy1 kdy1 reopened this Jan 26, 2024
@kdy1 kdy1 mentioned this issue Jan 26, 2024
Closed
@ShogunPanda ShogunPanda mentioned this issue Jan 26, 2024
Merged
@kdy1 kdy1 closed this as completed in #283 Jan 26, 2024
@kdy1 kdy1 mentioned this issue Jan 27, 2024
Open
@CatsMiaow CatsMiaow mentioned this issue Jan 30, 2024
Merged
1 task
@imranbarbhuiya
Copy link

Hi, is there any way to pass this flag --strip-leading-paths from .swcrc?

@ShogunPanda
Copy link
Contributor

Not at the moment. I plan to implement this in #284.

mrhyde added a commit to 2BAD/ryanair that referenced this issue Feb 7, 2024
@mrhyde
[conf] fix swc build breaking bug swc-project/cli#281
12e4d18
mrhyde added a commit to 2BAD/ts-lib-starter that referenced this issue Feb 7, 2024
@mrhyde
[conf] fix swc build breaking bug swc-project/cli#281
d5e5df1
@edloidas edloidas mentioned this issue Feb 12, 2024
Closed
JosephLeedy added a commit to JosephLeedy/express-magento2-client that referenced this issue Feb 12, 2024
@JosephLeedy
Fix incorrect path for production source code
fc8f04d 
SWC 0.3.0 introduced a breaking change which caused the production build to output to `dist/src` instead of `dist`.

swc-project/cli#281
@thomaswhyyou thomaswhyyou mentioned this issue May 2, 2024
Merged
@Hotell Hotell mentioned this issue Jul 12, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Add strip-leading-paths option
4 participants
@ShogunPanda @GNURub @kdy1 @imranbarbhuiya