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
One way this could work in the current state would be to use Excalibur as a git submodule and import the main entry point (something like import * as ex from ./lib/excalibur/src/engine). Although git submodules are notoriously tricky and full of sharp corners.
I found an interesting concept mentioned online called a "source package", which would be a separate package that would contain the raw source files and allow users to opt-in to source files https://stackoverflow.com/a/57534667, CRA has a proposal
@kamranayub@jedeen What do you think about exploring and potentially publishing a "source package"? Or does it make sense to include all the source in the main package?
Context
Sometimes while digging through code, it's useful to see the original implementation of a method.
Proposal
Include
src
in the published npm package, allowing "Go to implementation" in editor. Example change: ce8ec03The text was updated successfully, but these errors were encountered: