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

Release a new package with webpack 5 fix to npm packages #81

Open
oggy107 opened this issue Feb 2, 2022 · 7 comments
Open

Release a new package with webpack 5 fix to npm packages #81

oggy107 opened this issue Feb 2, 2022 · 7 comments

Comments

@oggy107
Copy link

oggy107 commented Feb 2, 2022

Release a new package with webpack 5 fix to npm packages

@oggy107 oggy107 closed this as completed Feb 2, 2022
@oggy107 oggy107 reopened this Feb 2, 2022
@imraazrally
Copy link

imraazrally commented Feb 11, 2022

It looks like the double semi-colon issue was fixed in the codebase but a new package hasn't been released yet. I pointed my dependency file (package.json) directly to build from the git-repo like this

"semantic-ui-css": "git+https://github.com/Semantic-Org/Semantic-UI-CSS.git"

But if you want to prevent your build from breaking changes to the trunk, you can fork the project and lock your dependency to a branch/tag. This is a viable short term fix

@Lord-Mendoza
Copy link

Any word on when a new official package will get released?

@mraible
Copy link

mraible commented Feb 28, 2022

I can confirm that this fix solves #82 for me.

"semantic-ui-css": "git+https://github.com/Semantic-Org/Semantic-UI-CSS.git"

@firrae
Copy link

firrae commented Mar 6, 2022

Would be nice if this was pushed out. It's making me serious rethink using Semantic UI if fixes like this don't get version pushes.

@oggy107
Copy link
Author

oggy107 commented Mar 7, 2022

Would be nice if this was pushed out. It's making me serious rethink using Semantic UI if fixes like this don't get version pushes.

exactly... I can't get the reason why they are not pushing it to npm.

@Lord-Mendoza
Copy link

For my project I ended up cloning this repo then republishing it on npm. You guys can just do the same for now. I agree they should just release a new version considering how simple change it needs.

@diego-iturriaga
Copy link

We are having the same issue in our project, when is it planned to release to npm?

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

No branches or pull requests

6 participants