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.

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

spack: naming conflict #1113

Open
tgamblin opened this issue Sep 26, 2020 · 6 comments
Open

spack: naming conflict #1113

tgamblin opened this issue Sep 26, 2020 · 6 comments
Milestone

Comments

@tgamblin
Copy link

Question

Hi there -- I'm one of the developers of a package manager called Spack:

We've built up a pretty large community with thousands of users and the project has ~650 contributors at the moment. Spack has been around since 2013. I'm worried there will be confusion between the spack bundler in swc and my project.

Is there any chance this spack could be renamed?

@kdy1 kdy1 modified the milestones: v1.2.35, v2.0 Sep 27, 2020
@kdy1
Copy link
Member

kdy1 commented Sep 27, 2020

I'd like to, but as it's a breaking change, I think I can only do it with v2.0

@tgamblin
Copy link
Author

I think I can only do it with v2.0

Thanks!

@tgamblin
Copy link
Author

Do you know when 2.0 is likely to be released?

@kdy1
Copy link
Member

kdy1 commented May 23, 2021

The core feature of v2 would be a babel plugin support so... I'm not sure about the time but it's not so far.

@kdy1
Copy link
Member

kdy1 commented Aug 10, 2021

I'll fix this with 0.2.0 of @swc/cli, instead of breaking change of @swc/core.

@kdy1 kdy1 modified the milestones: v2.0, v1.2.77 Aug 10, 2021
@kdy1 kdy1 self-assigned this Aug 13, 2021
kdy1 added a commit that referenced this issue Aug 13, 2021
- Rename `spack` crate to `swc_node_bundler`. (#1113)
@kdy1 kdy1 modified the milestones: v1.2.77, v1.2.78 Aug 13, 2021
@kdy1
Copy link
Member

kdy1 commented Aug 14, 2021

I found that spack.config.js cannot be renamed without a breaking change.
I think about a solution, and it can be renamed if @swc/core should accept two config file names while it's v1.

@kdy1 kdy1 modified the milestones: v1.2.78, v1.2.79, v1.2.80, v1.2.81, v1.2.82 Aug 15, 2021
@kdy1 kdy1 modified the milestones: v1.2.82, v1.2.83, v1.2.84, v1.2.85 Aug 24, 2021
@kdy1 kdy1 modified the milestones: v1.2.108, v1.2.109 Nov 7, 2021
@kdy1 kdy1 removed their assignment Nov 15, 2021
@kdy1 kdy1 modified the milestones: v1.2.109, v1.2.110, v1.2.111, v1.2.112 Nov 17, 2021
@kdy1 kdy1 modified the milestones: v1.2.116, v1.2.117, v1.2.118, v1.2.119 Dec 1, 2021
@kdy1 kdy1 modified the milestones: v1.2.119, v1.2.120, v2.0.0-alpha.1 Dec 10, 2021
@kdy1 kdy1 modified the milestones: v2.0.0-alpha.1, Next major Jul 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants