Tal500

> As @madeleineostoja pointed out, there should be a reason why REPL may have not worked in `svelte-table` case. Coz they would have had similar setup right. I think that...

BTW I recommend seeing the newly published library [leveluptuts/bookit](https://github.com/leveluptuts/bookit), though it's still experimental. It is presented in [the following youtube video](https://youtu.be/aOBGhvggsq0) .

Found the video with the misleading name! Rich Haris's video about packaging (first part of it): https://youtu.be/qD6Pmp45sO4

Hi! Any update?

> @thecodejack ok, but #105 as far as I can see does not expose the inputRef ? Indeed, #105 doesn't solves this. Notice that I have a giant PR #107...

One thing that I am now afraid about is that when you export the variable `inputElement`, you allow it to be modified by the user (Svelte doesn't have readonly props,...

I thought about some good compromise. Change the var to be the internal variable `_inputElement`, do not expose it, and use it(and only it). Then, define the following lines of...

> > I thought about some good compromise. Change the var to be the internal variable `_inputElement`, do not expose it, and use it(and only it). Then, define the following...

The correct Svelte way is to use [SvelteKit Packaging](https://kit.svelte.dev/docs/packaging) for the whole library. The directory "Examples" should be under routes (except helper component in a different folder). The code to...

Just add "type": "module" to `package.json` *edit*: I mean to the maintainers of this library to do so