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

Migration to npm #16

Merged
merged 2 commits into from
May 28, 2024
Merged

Migration to npm #16

merged 2 commits into from
May 28, 2024

Conversation

Legitgoons
Copy link
Collaborator

Description

  • 해당 이슈로 인한 storybook build 과정에서의 오류 발생

Changes

  • yarn에서 npm으로 패키지매니저 변경

@Legitgoons Legitgoons self-assigned this May 28, 2024
Copy link
Collaborator

@BangDori BangDori left a comment

Choose a reason for hiding this comment

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

많은 라이브러리들을 살펴보았는데, npm으로 관리하는 라이브러리가 굉장히 많은 것 같더라구요.

제 생각에는 라이브러리 자체가 많은 dependency를 가지고 있지 않아서, 패지키간 의존성에 대해 크게 고려하지 않아도 되서 유저풀이 넓고 간편하게 사용가능한 npm을 사용하는 것이 아닐까.. ㅎㅎ 하는 생각을 해봅니다.

고생하셨어요~

@Legitgoons Legitgoons merged commit f947688 into main May 28, 2024
@Legitgoons Legitgoons deleted the feat/migration-npm branch May 28, 2024 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants