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
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
It is useful to create npm packages that reference types defined in @sapper/app, @sapper/server, @sapper/common, @ @sapper/service-worker. However, these modules are defined within a sapper project in the src/node_modules directory, making the task of referencing these types from the npm package impossible (or not obvious).
It would be useful for a package author for these types to be defined in the sapper npm package and have documentation on how to reference these modules.
The text was updated successfully, but these errors were encountered:
btakita
changed the title
Expose @sapper/app, @sapper/server, & @sapper/common types to npm packages
Expose @sapper/app, @sapper/server, @sapper/common, @sapper/service-worker types to npm packages
Mar 12, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It is useful to create npm packages that reference types defined in
@sapper/app
,@sapper/server
,@sapper/common
, @@sapper/service-worker
. However, these modules are defined within a sapper project in thesrc/node_modules
directory, making the task of referencing these types from the npm package impossible (or not obvious).It would be useful for a package author for these types to be defined in the
sapper
npm package and have documentation on how to reference these modules.The text was updated successfully, but these errors were encountered: