rp
12/17/2020, 2:45 PMrp
12/17/2020, 2:46 PMrp
12/17/2020, 2:46 PMuser
12/17/2020, 2:48 PMrp
12/17/2020, 2:48 PMlaznic
12/18/2020, 7:28 AMrp
12/18/2020, 7:30 AMrp
12/18/2020, 7:31 AMlaznic
12/18/2020, 7:32 AMBBB
12/18/2020, 1:25 PMrp
12/18/2020, 1:32 PMrp
12/18/2020, 4:26 PMBBB
12/18/2020, 9:28 PMBBB
12/18/2020, 9:28 PMrp
12/19/2020, 1:11 AMRahul1234567890
12/21/2020, 8:42 AMeshnil
12/21/2020, 12:46 PMrp
12/21/2020, 1:28 PMuser
12/21/2020, 5:25 PMcp
12/22/2020, 12:21 PMkevin.a
12/22/2020, 12:25 PMkevin.a
12/22/2020, 12:25 PMsupertokens-react-themes
with supertokens-demo-react
project in the first place?kevin.a
12/22/2020, 12:27 PMnpm run start
from supertokens-react-themes
repo directly?cp
12/22/2020, 12:28 PMcp
12/22/2020, 12:29 PMkevin.a
12/22/2020, 12:32 PMkevin.a
12/22/2020, 12:33 PMbuild
command. How do you intend to modify the theme (written in typescript) without building? Seems like even if you copy it you will still get the issue.cp
12/22/2020, 12:40 PMkevin.a
12/22/2020, 12:42 PMkevin.a
12/22/2020, 12:47 PMsupertokens-react-theme
locally inside another repo such as supertokens-demo-react
, you will have to remove conflicting modules when running locally. Note that this issue is only happening in local environment. That's why it's recommended to simply run npm run start
when you want to modify a theme, and then from your project, reference the remote package (on github or npm) after you have made your changes. Does that make sense?