Can anyone help me figure out what I'm missing here? The npm build command which is used in the GitHub action creates a build folder.
The dist folder, which is where the package.json defines where the exports come from, is setup inside the tsconfig.json file but I don't see when is that in any way triggered.
Right now, the files I need when I'm importing from the library don't exist. All there is is a build folder with the React app itself.
I did, I looked through the github repository and noticed the npm run build command was replaced by tsc, instead of the original react-scripts build. That's not mentioned in the article.
I don't quite remember if that's all that fixed it though, I think it should. Looking through the repo certainly helped.
Indeed that helped!
One more thing I had to change was the noEmit setting in "tsconfig.json" to false, as explained here: stackoverflow.com/questions/590557...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Can anyone help me figure out what I'm missing here? The
npm buildcommand which is used in the GitHub action creates abuildfolder.The
distfolder, which is where thepackage.jsondefines where the exports come from, is setup inside thetsconfig.jsonfile but I don't see when is that in any way triggered.Right now, the files I need when I'm importing from the library don't exist. All there is is a
buildfolder with the React app itself.Did you find a solution for this?
I did, I looked through the github repository and noticed the
npm run buildcommand was replaced bytsc, instead of the originalreact-scripts build. That's not mentioned in the article.I don't quite remember if that's all that fixed it though, I think it should. Looking through the repo certainly helped.
Indeed that helped!
One more thing I had to change was the
noEmitsetting in "tsconfig.json" tofalse, as explained here: stackoverflow.com/questions/590557...