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

Diez with create-react-app target without changing webpack config. #131

Open
pwbuys opened this issue May 28, 2020 · 1 comment
Open

Diez with create-react-app target without changing webpack config. #131

pwbuys opened this issue May 28, 2020 · 1 comment

Comments

@pwbuys
Copy link

pwbuys commented May 28, 2020

Good day. I had no difficulties getting started with diez. However, when trying to add diez to my own react project, I was unable to get the integration working. Especially hot reloading.

I have a create-react-app and I am unable to compile the diez project once my web project dev server is running. When running npx diez compile -t web I am getting error

EPERM: operation not permitted, mkdir 'C:\yada\yada\design-app\design-language\build\diez-design-app-web'

If I try npx diez hot -t web i get

Compiling project...
Serving hot on port 8080.
Built in 3761ms.
Compiling project... # and nothing else after this.

Is it possible to get diez hot reload working without changing the webpack config for my current web app? I don't want to run eject

To reproduce

  • npx diez create app
  • cd app
  • npx create-react-app my-app --template typescript
  • cd design-language
  • npx diez compile -t web
  • cd ../my-app
  • npm install --save ../design-language/build/diez-app-web
  • npm run start

Up to this point I am able to get diez imported and the styles into my app. However, to make a change to the diez project, I have to stop my react dev server, recompile diez project and restart react server.

@pwbuys pwbuys changed the title Diez with create-react-app target without webpack config. Diez with create-react-app target without changing webpack config. May 28, 2020
@stale
Copy link

stale bot commented Jul 27, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 27, 2020
@stale stale bot closed this as completed Aug 3, 2020
@roperzh roperzh removed the stale label Aug 4, 2020
@roperzh roperzh reopened this Aug 4, 2020
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

2 participants