Author: Jimmy Dagger

It’s not the only way, but it helps so I I will talk about that and it’s not going to be me talking alone. So, if you have any question at any time, stop me and ask your question just straight.

You know, don’t don’t wait for me to a slide or to slide, or I hope it will be interactive. So yes, so we go through how current package system work then some of the issues with the way it works right now how we design package. When should we create one, why should we not and actual practice without publishing, I will need a volunteer for demo, will not go through the end of the story, but will just try to go through and at some points we just not publish it and then so.

This volunteer will work on the creation of a package and then I will show the update of a package with one package that need updating. So that’s it. Let’s start so. First, the mm package repository so who one here has already seen these websites? Okay, so I guess the others have not been using the Elm yet now. So this is like your homepage when you are doing Elm developments. This is a very simple page.

You have a search engine here, quite basic. Basically, you can just search for things that are in the name of the package or the username of the creator of the package or the description of the package, and that’s all we. You have some fancy search online for looking for types of functions, but I’m not sure it’s working very well, because I sometimes I try to use it and yeah. I don’t know so. You have on the right side, interesting resources like basic guide of how to use package and design guideline for API, for documentation, etc, and just below that you have links to the most common packages in Elm.

So whenever you have a question about which function, how this function works or how this other function works, you should find it here. Usually it’s in core. If it’s core elm function or whatever things you need, yeah, yeah, it’s, okay, it’s a it’s quite small! I have the link later so we can, we can go there, humans, that’s at some point, yeah, it’s it’s just generic guideline. It’s not very specific! It’s just telling you what you should do.

What you should not do is strong, but we go there. So the first thing you have to know about packages is how to describe the package. So in NPM you have the package that JSON file that describe your node package and in Elm you have the Elm package that is inside. That soon will be a bit different. Hello, so it’s quite simple: you describe the version, so this is what what the what this side looks like when you new project you don’t have added any other dependency, everything it’s basic yeah, it’s just how it looks like at the beginning.

So version summary where you put the summary of your package: where are your package live so on? Github will tell a bit more about that later, the license of your package, so by default. I think it’s BSD 3 for everything you can choose something different. Of course, the advantage of this license is that it’s very permissive, so you can reuse those packages in any open source, project or private project.

If you want to relicense it – or I don’t know, do anything that is cooperative with it yeah it’s it’s roughly like MIT. It’s a little less permissive than MIT, but it’s rough like MIT and at the other end of the specter you have like the GPL license, which is really copied. I’ve stated everything you have one GPL file, your whole project must be GPL and in between you have like the MPL license, Montilla public license, which is more permissive.

You can reuse an PL file in other projects which are not MPL, but the file still needs to stay NPO. So it’s more flexible and you keep the fact that the one thing you wrote open source is always distributed as open source. So then you have the folders that contains your modules. Initially, it’s just the current directory yeah. You have the exposed modules in those folders, because you don’t have to expose everything you can just expose a few different models of your package and the dependency or package depend on so we’ll see how it works a little bit later, but basically say the name of The package and then the version of the package, so it will be always something like that.

We’ll explain it later and finally, the version of M you are using because of course, enemy is very opinionated and not like Python. For example, when the main version changes, everyone has to change to the main version. Otherwise the ecosystem is not as good at it should be, so you always have to specify the version you are using so that other people know and system knows if it’s compatible. So how to install package it, it’s simple! Actually, if you have Elm installed on your computer, the best way to install the package is just find the package on the repository.

We do well website repository and then you have the name of the author. The version of the name of the package – and it’s just an package in some this thing so this it will change the didn’t file by adding a new dependency here and downloading the source of device and put them in some special directory. So yeah quite simple. There is another way to do it so, instead of just using L package install which will put a new line in the dependency here, you can just put manually the new light in the dependency and then call M package install without anything.

So if you have a lot of package to install at once, you can just add all the names here in this file and then do an install M packaging sudden. It will insult everything you don’t have to use and pack any style, the first one and package. It’s all the second one. Actually I don’t know if you can do L package in seven, then multiple packages does anyone know, don’t do white. Only that’s true yeah yeah.

If this way you have to do it once so um using a package quite straightforward. If your package, I will take the example of this package mouse: this is the github repository and the package is available in here mouse in and oh I’m trapping in my own game. So here, for example, there is one module in this package, so this thing reflects the with me of the package and then the modules are here. So there is a mouse module which has a few different types and functions.

So if you want to use, for example, the mouse module inside the Mouse events package, nothing complicated you just in your in your file like main dot Elm, you just import Mouse. If you have install it before with this or this, it will just work. So just import the modules of the package you have already installed and it’s okay, removing a package very good mouth yeah same module name, it doesn’t work yeah.

So there are very rare issues like this one, but there exists between different projects. I think there is even one between the style elements and the CSS, but what you should do usually is try to namespace your toward your module like, for example. No, no, because you multiple people can have same module names its if it’s not in the same context. There should never be used at the same time, so elm doesn’t prevent you from publishing the package with modules that have the same name than other packages yeah, so you can.

But what what you should do, if your use case is not really specific, is namespace. Your modules like, for example, so this is this – is a package called a pencil geometry. It’s to do some geometric stuff, and here all the Acacia name, our name space with open solids, so that, if you want to use these packages, you cannot have any conflicts with other. I don’t know other library that will have the vector 3d module or something like that, which is which can be quite common.

If you compose difference in your algebra library, organized vaulted stairway on alias, you can alias the import, but after importing like you can use import something as something else, but the import something will not work. If you do it two times, if it doesn’t know which one it is yeah my name, so in that situation yeah, you can do anything yeah, it’s good, but I mean people try, because if it’s two projects that are likely to be used together, usually the our Thoughts are know that there are likely to be used together, so they try not to use the same names, mmm module names but yeah it can happen so removing a package.

I don’t think there is a comment for removing a package, so what you have to do is just remove the line in the package.Json file and then you can try to remove only the module things that are inside these folders that are related to this package. But you really, usually you will just remove all this directory, which is where Elm puts everything it needs the sources, compilation and everything. So just remove this one and yuri downloads, the packages and yuri compile the packages I mean it will redownload it automatically, but it will just take long longer time to recompile, but it’s safer to do it this way, so the versioning of the packages, when you specify A package you specify a version like this one and what it means.

It’s that the meaning actually is really precise, like the versions of package are semantic and forced meaning is just not semantic that you choose the semantics, it’s a semantic that is specified and that is enforced by the Elm compiler. And what is enforced is that you have three part in version: a major minor and a patch. So a major change meant means that there is a breaking change in in the code.

So, for example, one function doesn’t have the same signature as before, or one function was removed from a module or when module was removed, or one type has changed hello, so you mean the implementation inside. So it’s just a patch, so internal yeah. It cannot be a breaking change if signature doesn’t change the B, yeah yeah, of course, yeah of course, of course, but yeah. So it’s it’s just it’s it’s the behavior yeah.

So what? What means is that you will not have a compilation, error or runtime error, because you never get a runtime error, but you will not get an error, a language error with a patch or a minor issue. But of course you can get like behavior. Your logical error. Yeah yeah, you cannot prevent that. Maybe we can in a few years I don’t know so major, so something break. So that’s why, when you specify a dependency of a version, if you know it worked with this one, you know it will work until the next major break, so you won’t have any issue.

This may not minor is the second. It means that it is a non-breaking change, but something is still important, like a new functionality that was not available before, like you have a new module or you have a new function or a new type declare somewhere. So usually it’s new stuff and then you have the patch modification, so these are just transparent for the code like for the compilation aspect of the code, meaning like the documentation shown or an internal implementation change, but it won’t change anything for the users of the package.

Yeah, I’m actually enforce this versioning. Although therefore, so when you try to publish for the first time a package, it must be 1.0.0 and then any time you want to update a package. There is a comment which is an package bump and it chooses the new version. It’s not you chooses it, it chooses the new version and it modifies it modifies automatically this yeah it. It analyzes your the type signatures of all the of all your your codes, and it basically has rules like these ones.

So if there is a if there is either only new stuff is just non-working change. If there are stuff that are changed from the last time, you publish the package, its breaking change and that the current to the last one that was published and with the the next one that you are going to publish so the one that is in your current Workspace workspace states of your gig project, because every fine everything is version with kids, so you know, because you have to put it on github, any other questions about this.

No okay, so yeah. The good thing with enforcing versioning is that you never have a breaking issue, because some packets just thought that they were doing a minor change, but actually it changed something major for someone else: okay, so a few drawbacks of the system, the packaging system. First, it’s hosted on github, so this is something that even said. He is also a priority. I guess not really high priority, but they want to have their independence from github at some point, at least for the version that has already been published.

But right now it’s not the case, so you don’t control github, so anything happens to get up and doesn’t exist anymore yeah. So, for example, oh yeah, it’s just how it works. So when you use the M package command, you exchange information, we’d get up and with the M package website. Oh so that has a few things that are stalled inside there, but every data source and everything is pulled from github.

So, for example, I had an issue. One time where I wanted to use a package that was published all the documentation, everything was an unpackage and when I tried to use it, I had an issue with github. I was thinking that my connection was broken. It was just that the author of the package removed the package from Garib, so you couldn’t download it anymore. So every package that, depending on this one, could not work anymore, yeah so and please do which website with actual yeah, when you publish it close a few things like documentation and the descriptions of the M package JSON.

But the sources are not fetched. So only some descriptions – or I think it’s fetched like the type signatures of stuff, but I’m not sure I think it’s HTTP not SSH, because you don’t have to set up an SSH to use it so but yeah, because if Elm wanted to use it with their Own token or stuff like that, it will, I mean I’m not sure they could use it every time or for every user, every Elm user. So I think its uses ATP HTTP, but it’s not an issue for public packages because you can always access them with HTTPS.

So another big issues with the package system is that for now from 0 18 to change in 0 19, all things are installed locally in your project, folder, so meaning you want to create a new project that just depends on the core and the HTML thing that You have already installed in five of your other project. You cannot do it or you have to manually hack it by copying and pasting things by hand, but the normal way using I mean style, something it will have to pull again the things from a github and to put it inside your am stuffs directory.

So inside this thing you have different things. You have the sources of the different package you are using. You have the the build artifacts that are already being built so that you don’t have to rebuild everything each time you you make you compile, and you have a file that gives you the exact dependencies so that you could use this one to reset up the project. For something else, I think it’s useful for analysis thing and to know exactly what is installed in case.

You have a minor change that changed the behavior of an example. Yeah you see right now is the case. So are they going to change it in early 1990? Installation with FN, you cannot say, 100 %, but it’s been said in different medium of discussions that it’s going to change like they want to have in your home space in your home directory like a dot, Elm folder or something similar in which every package you pull.

Will be inside install in this hidden, folder or hidden directory so that each time you reuse, a package that you have already downloaded already compiled, don’t have to do anything it’s just compiled and downloaded in your home folder somewhere and you just pull it and it works. Yeah, so I think it’s going to be this way, I’m not sure another issues that we didn’t discuss previously with the packaging system of elm is that to make sure that you have the guarantees of El meaning no runtime errors and everything works.

When you compile, you cannot have Java scripts in your packages, so it’s Hjelm, 100 % or it cannot go to the package repository so meaning. If you want to use a Java Script package, which is in NPM, you have to rewrite it in Elm or to use ports. So if you know what port is, there are the mean of discussing between JavaScript and elm to make an interface of the different api’s. So it’s growing like you.

If you go to this web bust and read it, the guy will say that there are currently this amount of packages is just scrolling and just one javascript comment to count the number of things that and the pack and the websites, and it’s say that he says That six months ago there were like 200 or 300 packages, and now it’s almost 800, so it’s growing. So, even if sometimes elms people think that Elm is stale or stealing it’s not it’s just that the master branch is of the development are still because they are working on the dead things and they do major update rly slowly that it’s going to be a year.

Now, since 0:18 has been out, so it’s read stable, actually, even if it’s not a stable version but yeah. So soon we will have 0:19. I think, maybe a month or two look like that. I know it yeah, you don’t know, but I knew there’s like a few packet, but everything that I was looking for. I always kind of found something I’ve not been using a lot of web development packages, but I know there are Web API that are missing that are important, like using database yeah, that your custom package between stone with another, but you can always make it work yeah.

I found that most of the time when you need something at least one person has found like yeah – it’s not always easy to give in stuff yeah yeah yeah. You can do that, I’m not sure you should, but sometimes you can. Okay from the individual personal point of view, there is nothing wrong with it from the community point of view. It can encourage people using javascript in Nome and it’s not the way that wants to be developed, because in the end, right now, javascript is just a compiling platform.

So if you are using javascript in a package, it means that you are committing to JavaScript and at some point, for example, if everything is going to be compiled to web assembly or whatever language. Your code is not working anymore, yeah, so yeah yeah, of course, and we will have like children before it’s compiling to something else, so yeah yeah. I think I think at some point it will compile to webassembly, but the web assembly ecosystem is not mature enough.

Yet because it doesn’t have a garbage, collector, two languages that don’t manage their memory themselves, but yeah yeah, it’s yeah and you’re – probably fine, but but seeing for the community like to see whether we can solve the problem and a lot of things have actually shown up To be very nicely solvable attraction, so I think that’s sort of it’s also, I think, trying to encourage people to write Elm to develop em code that do things that are already done in other languages, but better so yeah.

So you just talk about it. What do you cannot with the M package official system? You cannot install private repository or repository that lives somewhere else then get up on that on github or on your machine. So to do that, you have two tools. You have a little bit so that you mentioned before, and you have another one M groove that are basically replaces M package manager, so it can install local packages and github native and effects manager packages, but yeah, as we said before, you should use it only if You know what you are doing and if you don’t want to regret it later, is the best adjudication before building a large number of mortgage insurance right, yeah.

So few designing steps for your package. So when should you create package on? When should you not, so you have general guidelines about creation of the package, so the guidelines are there. So it goes through this point. So when should you create a package? So when you have something special, you want to take care of. Not try not to do something to generate too general yeah. That’s the no Haskell point, because you know sometimes they want to do something too.

Generic right, good documentation. This this one is really interesting. The data structure should be the last argument. It means that when you design the thing, the looser you design your your API, if you put the data structure or the men data of your offer function as the last argument, you can reuse it in the function that is after in your flow of computation, and You can use the pipes syntax in Elm.

I don’t know if you know about it. If you don’t know just it’s explaining the in the guide, but it’s really nice to to make a flow of computations and see how things evolved little by little. So it’s a really good advice and then few things about namings like don’t use, three-letter namings like don’t use, CLA three-letter abbreviations, avoiding things operator so in fix operator without a name because it’s not usable if you want to research them on the package and functions.

If you want to know what what it’s doing it’s better to research, something with a name with letters so yeah, these are basically the main guidelines, and so then, once you know about that, when you want, when you think of creating a package, you should ask yourself At least these questions so does the feature you want already exist somewhere. So you have to look on the package, the EM packet website, of course, or so on.

Github. Sometimes, packages are not public published in github, but someone has already done it and if it’s not available, is it just a small extension of something that’s already exists or not? If it’s some small exemption of something that’s already exist, the better way to do it is just contacting the person that is doing this repository. You can contact them, usually through github, with issues or just elm slack.

If you like that and discuss it’s the best way to grow the community and to have the things, maybe sometimes you didn’t even think of something and the creator of the package know the reason why it didn’t do the thing you want to do and if you Better inside of what you want to achieve Indian, so then are you sure you need this? If it’s not just something, you need one time in your project, it is, it was just something you have been using repeatedly and you think back here should be useful and is this something that is implementable only with L, no JavaScript, because otherwise you cannot create a Package on package and is your API? Okay, not too generic, but not too specific, either like just in the right balance in the middle.

So once you decide you create a package. What are the things you need to do? Okay, so first we said contact authors of similar packages and asked them if they are willing or if you can, with a pull request, implements your new features. If they are not verified that the package you want to create as a unique, because it’s a mistake that some people did including me creating a package name that has the same name of someone else.

And it’s not a good idea. Because then, when you want to reference it, you have to reference it with the full name, and sometimes people look for it and they don’t know which time which one they want to choose, because they are the same name, etc. So try to be specific about what you are doing in your package with a specific name then add license and read me so it’s basic advice but yeah. You have to do it.

If you have images that you want to add in your Whitney images, for example, that are inside the repository, github can display them, but when they are published on the embedded web sites, there will not be visible, because the M package website is not get up, so They don’t have access to things that are inside the repository. So if you want to add images, visuals in your package for in the readme use something else with absolute reference of the of the image.

So what good advice for this is that on github, for example, every user in github can create your username, get AB dot, IO repository and inside this repository. Everything that is inside this repressor will be accessible through static, statically accessible from github. So you can put an image you can put an image somewhere inside there and this link will work and will display the image even in the Ruby in the package manager.

So it’s better. If you want people to see your images in the package manager, not only in github, so you have guidelines for the documentation which is alright for the documentation also, and you have a way to preview documentation. So this is really useful and we’ll use it. I guess in a few minutes and then also try to do tests and provide examples for your package of the right people and we’re going to use it, and people are not going to helps you with your package and implementing stuff on whatever okay, so actual table.

Shing so first package release we’ll need a volunteer who wants to try to do it so who has never published any package here so who volunteer yeah so so I’ve created a folder here like meet up. There is already some some stuff inside I’m going to remove this huh nah. I think star will work nope. Oh yes, yes, yes, mm, yeah! Okay, so there is that git folder left it’s okay, so yeah yeah, because it’s not mirrored no so yeah.

So first we will initialize the repository so to the git repository I’ve already initialized it. So you don’t have to initialize it. It’s a good idea to put a git ignore file in all your repository, because you don’t want to put something online that shouldn’t be online. So there is a website that called getting an order. I oh that’s, really useful. You just put the different things you are using like y6 Windows, Elm whatever and then gives you a fight.

So usually I do just this. We get the the file and I put it in a meeting no file yeah, but it’s it’s okay. It’s really done. I think you know it’s not done. I know it’s not done so yeah. You can do this if you want oh yeah, no, not working now. Whatever forget to the Gugino file, so with some by initializing the package, so even yeah you can do L make even in a empty directory, so it will create a few things.

It’s a French keyboard. Yeah. Are you? Have a Japanese keyboard, [ Laughter ], so the Elm yeah Elm is asking you if you want to install shoe things. So it should not do this it’s just because the window is a bit small but yeah. So it has compelled 37 modules yeah. We thought we had only three models but yeah, it’s because it there are modules that depend on other models that are not public modules, because there are multiple models in each package.

So that’s why, but once we have done it, we don’t have to compile anymore those ones, so it will be faster. Okay, so do we want to create what project do you have in mind? What kind of or anyone anyone want to project something to create something? Like I don’t know what but left was it like string padding or like? If you have some string, you planned it left with some zeros or some spaces application to purl left yeah yeah, whatever you can, you know, create some fatalistic humans, so I yeah.

Usually it’s better to put everything in the in a in a folder, so create a source folder and then create your module. So yes, do you use V more? No, but then then it I have. I have also Adam, I think, yeah yeah we just had to. Maybe you know I need to make a new file yeah, usually for me. I have eat, I type anything from an editor. I don’t know type whatever you want. You can use yeah. I think so.

I think oh yeah I have to create, so you have to find a name, that’s all item and then I just lift yeah. I think it’s a good name. You know if I just type item before you will greet your father. I think so either add some experts here, yeah, oh yeah, it’s not installed, maybe a little bit after left L meter. So whatever you want yeah yeah and they use it, use what she wants. Maybe it will be easier: okay, okay, okay, okay, we’ll just we just enter in edit mode and to be okay, so we say bad left, no bad left! Oh damn yep! Okay, so maybe we can decision the right so that we can read the error messages there.

Yeah, you click here and you move this and right. You got it yeah, not a click! Click! Oh no yeah! It doesn’t work. Sorry, [, Laughter, ], yeah, yeah, it’s only uh, sorry, so insert with ii yeah I right and then yeah you can right. So you know bit of hell yeah yeah yeah, but I never wrote another from scratch. It’s like main what you see you some bad module, little M, it’s a long, okay and then the name of the module.

So it’s a left, we’ve yeah upper! No excuse me exposing and then yeah exploding and then inside brackets two points, so we will expose everything for now. Yeah, okay, okay, today mean like, depending if you were doing like a beginner program or whatever program you put me know because we’re not going to do a program just a package, so we don’t have it. We don’t need any main. So we can just start with the function.

One function we want to expose, so I think we can call the first function like at left or something like that with little P. So the first thing is the name of the function name of the function yeah. So this is the type signature, so it takes us rings and returns a string yeah. The arrow is somewhere here. Yeah. Oh yeah! Sorry, that’s! Okay! Sorry! I can I can view here like I have the modification here, but then I can also just if it just says a small education yeah at the notification there, but it’s okay.

Okay, hopefully we’re live because we are missing some sound for the article. So where was I so it’s committed? Then you have to tag so one thing that is a bit redundant is that you have. The version is in the in the package file, but you have to tag it for get or so so that’s the end package websites knows which source it has to retrieve. So we will tag it. It’s version 1.1, that one okay and then we push everything, including the tax.

If we didn’t push the tax, it would not work, it will say it was that it’s not working. So, in the end you just use em, like aah, publish its verifies that everything is in order so and there it is life it should be. Actually so we have this. That is updated. So now I can click on the button. If internet works yep and it’s 1, 1 1, so quite easy. Just few commits change face bump automatically. You try to run your test and everything so that it works, that you don’t push version that don’t work and that’s all yeah thanks a mess if they don’t match it’s a mess, but I don’t know what mess it is.

I know that at some point I I tagged something what is really really annoying it’s when you think it’s going to be right, so you tag your code and you push it on get up, and then you publish and something is wrong either in the publishing process Or you, you made a mistake in your code and something like that and when you do this and you if the publish is, is wrong, for example – and you have to redo modification you have to redo bump and you have to eat, will bump to another version.

It’s it’s! It’s a bit mess. So if something like this happen, the best thing, I think is just to undo the the commit, keep it as stash and redo it correctly, but an undo undone tag and we tagged it correctly. You can you can remove the tag on github. You know there is a comment, but it’s not removed automatically. If you remove it locally, so you have to manually, remove it and change it and get up, but in practice I don’t know exactly what happened.

If you do the same thing, you do, you know some Peter we do have them take. It is only exactly one thing: yeah sure I mean tags are quite if it’s the wrong tag, maybe the publishing was not will not work, because now, if it’s a wrong tag, an package will not find the tag that is corresponding to the version. So it will not be able to download the code, so I think that the publishing will not work yeah yeah yeah, so I think it will not work.

So what is going to change soon? Absolute, we don’t know there is a road map about the N language. It’s been written since April and it has not changed since yet so it described a few things that even want to work on, including what is going to main evolution for the next version. So the next version is specifying is specified for single page application. So, basically, how we improve Singapore application for elm, using things like server-side rendering for the first initial answer, so that you can have better reference reference thing from Google Yahoo and whatever it’s going to build, which back in for their son Joffrey.

For me, we don’t know. We don’t know, but I think it will just generate HTML and CSS, that you can use yeah. Maybe after you just have to manage your own server Unser’s, I don’t know I have no idea but yeah it will be. I guess the back end will be node. It’s it’s always it’s already working with no, no, but I mean what people usually use on back-end our confession. I think it should not be confused with actual yeah yeah articulate Li where they pulled out yeah yeah yeah.

It’s not intended to compile everything all to run on the server it’s just for the first page and to load quickly, so they’ve improved a lot of trimming of the unused code. So currently, when you compile your code to JavaScript, every module that is needed is compiled on including the JavaScript code when you gzip everything it’s already pretty small, smaller than others framework, but it’s going to be from from Evans word: it’s going to be like a massacre Like that, it’s going to be far smaller than what other competitors do for the assets you are serving yeah and basically it will improve the the way you can spit your different code, your different part of the code, if you are doing multiple page in different modules, That you don’t have to load all the pages on the first page and open it, but what it means for the package specifically, is that be careful that what I’m saying is not official.

So things are going to change and there is going to be a difference between what is a package and what is a project so right now there is the same Elm package to Jason for things that are supposed to be published on em packages and things that Are supposed to be just personal projects or just webpages on whatever, so there is going to be a difference. So in the new and G’s on file, there is going to be a type field which specify if it’s a package or not a package and then a few different things.

Now you don’t have the the link to the github repository. So I don’t know if it means that it still has to be github and it will figure out the link with only the name of the repository or if it. If there is going to be some other mechanism. I hope, but we don’t know, and another slight difference – is that there will be a difference between dependencies and test dependencies so that you don’t have to download everything if you are just using something, I’m not testing it and they yep.

I think that’s all, but any other question that you did not have yet yeah. Why don’t you make your own project after your mouse event, instead of trying to distill it off stream, the one that is already be given yeah instead of using the mouse events from Elmer that wasn’t possible upstream? What do you mean? I’r stranded try him and it was because you cannot send publishes to Eden. You will never accept, I mean it’s just he want to do things simple and what I needed for my mouse events are the positions of the mouse events and they are not provided in the HTML HTML module.

It’s. The only thing that is provided is the event. So in the event and the target, because you you put your event attribute on the target when you create your HTML in Elm, so what you mean is that is that if I follow my guideline, I should have asked even if, if he was willing to yeah, It’s not the only mistake I did with this one, because there was also another module called Elm Mouse events same name doing something a little bit different.

Yes, so it’s not the same functionality, but I should have asked him if he wanted to implement it my way, but it was just after another project I did. I did a package on the bouncing on and throttling, and I for this project I like when to ask all the other creators of packages similar and most of them didn’t answer. I get really nice answer from some of them, but when I try to implement thing, the first thing I did is using formats and formats and it was deal-breaker like they were not using D from M format.

So they asked me just modify what you want and don’t formatted everything, so I’ve ended up doing my part and my own repository. But yes, it’s a good remark. I think for Evan. For my defense, you yeah, I could have asked him, but it would not have changed anything so for all the projects, like the other one. I showed you before the open, solid, which is doing geometry things I participating in this project, and I made pull requests and issues and discuss with him to implement you things that I needed.

So this was better than just to implement myself everything, but all this one year I didn’t so it was a bad choice. I think it’s just legacy, or maybe he needs some special things, but he’s encouraging, even yeah, but even and which are, as advising everyone to use em format. So I don’t think so. Yeah yeah yeah. It’s probably that, because Aaron format is quite new, so I guess event didn’t want to reformat everything of we format all his codebase waiting for the next big release, which is going to happen soon.

I don’t know how soon but yeah, I think, that’s the main reason why I think just like, but there yeah and they are working in close relationship since, for example, the documentation, the add ducks and everything that you add in your package documentation. These things are both formatting and and important for the for Elm compiler, so they are working together to to say which, how we should format it and how it should appear and right cetera.

So I think it’s going to be used in the next release know we can check you can check so core mmm you’re fading. Do you remember one that was not full following the guideline or just I pick a list? Okay, so this one is not following Cleary because, for example, there is two spacers before we format, and it should be only one line per written. So, let’s see nope it works because that yeah. This is a good example right.

There’s an ongoing process in which he sometimes involves other people, it which is around how the modulation report. So so it’s not too concerned right now about the business thing concerned about what’s the next base, which will most likely change small things around what for module friction? Which will then in state to help augment the things that bound together and it’s quite aware of this facility publishing his changes and then hoping you’re, just hmm, okay, yeah.

I know that Ellen says dependent dependencies and a lot of third-party modules. Yeah did you know. That’s part of you know whatever, whatever goes into something pretty good like it as part of its Bella, I don’t know. I have no idea. No, I know that Evan publishes. I mean it could, thankfully, with this initiative around Cordell community, some packages that were abandoned by Central Texas and community of those rows of the occasion and came to the right place.

Emmet’s usually mentioned things like prefers pages, publish them, because he knows that mr. Kent will always be a television or somebody else provide support itself, which is also a way of distinguishing whether to come from with general, but it like community. It’s harder to tell this argument. I don’t know through the bed, but that’s assistant for this. That’s also why someone the co pages of the right, because of the day, all Benton.

I think it’s actually it’s not that much dependency that many dependencies. It’s just functionality that I’m not incur yet, and you know that should not be in core. I guess so, okay, so I think we mixed a bit together. The Degas someone

---