Remove dist files from source control #676
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dist files have not been rebuilt in a long time. I think they should be removed from source control and only published in the npm module, especially since there is nothing (a test, a script run on push) to enforce they are actually built. The result is that they're present but likely to be wrong.
To remove friction, I've elected to preserve the type definitions indist
, though they could be moved to a types directory.The files are still published to npm and may be retrieved from: https://unpkg.com/browse/regl/dist/
If this causes any problems (people retrieving outdated source files directly from github???), it can be reverted.