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

Test fails in semantic-ui-react/dist/commonjs/index #54

Open
RinkeHoekstra opened this issue Aug 29, 2019 · 1 comment
Open

Test fails in semantic-ui-react/dist/commonjs/index #54

RinkeHoekstra opened this issue Aug 29, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@RinkeHoekstra
Copy link

When running gulp I get the following error:

src/components/containerHome.tsx(2,9): error TS2305: Module '"/my/home/projects/UnSHACLed/node_modules/semantic-ui-react/dist/commonjs/index"' has no exported member 'Container'.
@jonathanvdc jonathanvdc added the bug Something isn't working label Sep 1, 2019
@jonathanvdc
Copy link
Contributor

Hi there @RinkeHoekstra! Thanks for your interest in UnSHACLed.

UnSHACLed was a group project that we developed for Ghent University's Design Project course. We haven't really touched UnSHACLed since last year. Now, two things are currently blocking people from using UnSHACLed:

  1. Judging by the error you've encountered, bitrot seems to have set in. I tried to build UnSHACLed from scratch and was able to reproduce your issue. I believe it is due to breaking changes to some of the NPM packages we use. Fortunately, I was able to find a package-lock.json file that should contain working package versions. Using that file, I have managed to build UnSHACLed locally, but the CI builds are still broken. You can find the file in PR Include package-lock.json file #55.
    There's also a pre-built version of UnSHACLed here: https://dubious-developments.github.io/release-candidate/index.html .
  2. More fundamentally, the server we used (http://193.190.127.184/) for running server-side collaboration logic to support UnSHACLed appears to have been recycled for some other project. Sadly, UnSHACLed doesn't work without a collaboration server.

We could solve the server-related issue by changing all references to http://193.190.127.184/ to, say, localhost. Users could then run their own collaboration servers and explore UnSHACLed.

But I doubt that any of my colleagues are up for that—everybody has sort of just moved on. Sorry. I know that's not super helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants