You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm confused here, when I install your package via NPM the contents of the chessboard-element folder inside my node_modules folder has a bunch of .js files that are nowhere to be found in this repository
I decided to fork your package so I can immediately use my click-to-move PR and when I tried to reference my fork inside my package.json I end up with an error because those .js files are not present
But when I install your package then they are present
What voodoo magic is at play here? Is there a command that needs to be run to generate the .js files?
I would love to have more information so I can get my fork working
Many thanks
The text was updated successfully, but these errors were encountered:
This project is written in TypeScript and the built JavaScript is published to npm. The difference between GitHub is expected and normal for compiled languages. You should only commit the source TypeScript files to git.
I'm confused here, when I install your package via NPM the contents of the chessboard-element folder inside my node_modules folder has a bunch of .js files that are nowhere to be found in this repository
I decided to fork your package so I can immediately use my click-to-move PR and when I tried to reference my fork inside my package.json I end up with an error because those .js files are not present
But when I install your package then they are present
What voodoo magic is at play here? Is there a command that needs to be run to generate the .js files?
I would love to have more information so I can get my fork working
Many thanks
The text was updated successfully, but these errors were encountered: