Disclaimer I really have no desire to maintain this project, as it's not mine to begin with. I was looking for something like Gitso but it didn't quite have what I wanted. After making my changes I thought I might as well put this up on GitHub for others who wanted something similar. So if you have issues, you're better off forking the project and fixing them yourself.

The only issue with this full-face respirator is that you can only buy it for commercial or industrial use. This means that unless you work for the purchasing department of a company, you will not be able to get one without a permit.

First off starting with the logo designs for both company's using same color scheme of Yellow and Blue. Both fonts are not the same fonts, but font layout kind of looks the same, as the letters overlap each other, in an almost same style manner.

A controller is the entity that determines the purposes and means of the processing of personal data. Some examples of a controller are listed below.DigitalOcean is a controller for our customer’s personal data (e.g. personal information provided to DigitalOcean when signing up for our services)A DigitalOcean customer may be a controller if they collect and process personal data on their customers (e.g. personal data provided to you by your customers)A processor is the entity that processes personal data on behalf of another entity. An example of a processor is listed below.DigitalOcean is a processor for our customer’s end-user personal data (e.g. A DigitalOcean customer stores their customer’s personal data on a DigitalOcean service)

In previous campaigns we created expansion material and used it as stretch goals. Going forward, we're just going to give it away from the start. So no worries on whether we'll hit it or not, you are getting this expansion if you pledge here.

The VTE widget was originally designed as the back-end for Gnome Terminal but was fortunately designed as a GTK widget so that other terminal emulator applications could leverage it instead of rolling their own. Many popular Linux terminal emulators use this component.

Ease of Use Write your model almost as you would on paper and Dynare will take care of the rest!

as a GUI for it, I use GitKraken

I read the negative reviews (the only ones that you can trust), but I bought it anyhow

Question: Why a cable for a wireless keyboard? Answer: .noScriptDisplayLongText { display : none; } <style> .noScriptNotDisplayExpander { display : none; } .noScriptDisplayLongText { display : block; } </style> because it is not a wireless keyboard...

Malware drive-bys are resolved rather easily with JavaSh-t block/allow lists. Some people might complain that blocking JS hurts the user experience but more often than not the people complaining are the ones wanting to perform mischief, such as malware, data mining and tracking.

Just my n=1 opinion only.

Snap packages can only be distributed through the Canonical store, i.e. they are linked to it. This brings some advantages like improved security but limits the developer. Conversely, Flatpak is not connected to any shop and this makes each developer the owner of the shop’s distribution. This is more in line with the open-source philosophy.

If there is one thing that normally characterizes the entire Linux ecosystem, it is that there are many solutions to one problem.

tcpwrappers or, as you’re probably more familiar, the hosts.allow and hosts.deny files

Highly Secure by Default

gsettings range org.gnome.desktop.background picture-options

Follow this link to the Hypothesis extension in the Chrome Web Store. If this is your first time adding extensions from the Chrome store in Edge, click “Allow extensions from other stores”.

distro that doesn’t patronise its potential users by fixating on an idealised use case drawn up in a meeting.

Generally, shrank is the simple past tense form of "shrink" like in "I shrank the shirt in the wash." Shrunk is the past participle being paired with "have" as in "I have shrunk the jeans." There are rarer examples of shrinked and shrunken in literature but not enough to support those usages as standard.

When referring to a change in direction, position, or course of action, the correct phrase is to change tack. This is in reference to the nautical use of tack which refers to the direction of a boat with respect to sail position. This phrase has long been confused as "change tact" but this is technically incorrect.

take care to discuss new ideas with facts, patience, and respect

Some passengers may have medical or religious exemptions. Indeed, there are legitimate medical exemptions, such as a history of severe allergic reaction to vaccines or other rare medication reactions. Pregnant passengers may be able to claim an exemption based on the limited data available in this population.

And while misinformation and outright lies about COVID-19 are still pervasive

the space has to escaped twice, once for the local shell interpreting the command and once for the remote machine interpreting it again.

Or use a '?' in place of a space as long as there are no other matching filenames than the one with spaces (since '?' matches any character): rsync -av host:a?long?filename /tmp/

What would make these units perfect is if they were mesh connected to a hub unit that could connect wirelessly to my internet connection. An alarm event would send me and alternate either a text/e-mail, or both. I could image adding a whole house water shut off that could automatically shut off the water to deal with a catastrophic failure when no one is home.

These thing can save you literally thousands of dollars associated with repair of water damage. I have installed one under every sink, dishwasher, behind every toilet, washing machine and refrigerator (ice maker water supply). Essentially, any place where there is a water supply to a faucet or appliance.

Fast forward two months later. The tank in the same hot water heater started leaking, and for who knows how long, because this thing did nothing. When I finally got to my heater, after discovering the water dripping under the floor itself, this unit was so soaked I had to open the battery compartment to drain it. Yes, there was that much water covering the alarm itself. The problem? Apparently, you need a significant amount of standing water for it to work. Because it was a slow-ish leak, and because the floor, although it was soaked, was draining and absorbing part of the water, and also because the water was draining through a nearby cutout in the floor, it never reached enough standing water.

After a bad leak from the pipe leading into my hot water heater left my floors soaked and damaged, I decided I wanted to be prepared in case there was a next time.

I improved its detection capability by taping a piece of paper on the bottom. It rests on the paper and absorbs water , setting the sensors off after a few seconds. Without this it wasn't able to detect water running down concrete with a grade. The water level would have come up a bit to trip the sensors.

For the price, why splice wires, the leads can be extended to 6 feet. What I would recommend is to place the sensor on a sheet of paper towel. Any moisture will wick up to the contacts. Also you can cover a bigger area where just a corner of the paper towel will transfer the liquid by capillary action to the contacts.

.noScriptDisplayLongText { display : none; } <style> .noScriptNotDisplayExpander { display : none; } .noScriptDisplayLongText { display : block; } </style> I am going to buy this and a 9v battery eliminator that plugs in(about $10). Never have to worry about batteries. If a Sump is involved maybe a very small UPS could be a solution(about $30). There is a mini ups on Amazon. You can get a 9v battery clip and wire up. Good 9V batteries aren't cheap either. Consider wha… see more I am going to buy this and a 9v battery eliminator that plugs in(about $10). Never have to worry about batteries. If a Sump is involved maybe a very small UPS could be a solution(about $30). There is a mini ups on Amazon. You can get a 9v battery clip and wire up. Good 9V batteries aren't cheap either. Consider what repairs could cost.

In American usage such divisions are generally referred to as colleges (e.g., "college of arts and sciences") or schools (e.g., "school of business"), but may also mix terminology (e.g., Harvard University has a "faculty of arts and sciences[2]" but a "law school").

often wrongly translated as "Dresden University of Technology"

It is a perfectly cromulent word. :)

Nice use of “embiggen” as a class name!

Chris, to address your “magic number” concern, instead of doing line-height: 0.5, you can use percentage-based positioning (top: 50%) on the pseudo-element.

Maybe there’s a technical term that I’m not aware of for this type of centered line-splitting heading.

Melamine is considered the black sheep of the sheet goods’ family by most carpenters. Typically because it creates a lower quality cabinet than other materials. But, also because it is so darn hard to construct with without getting chips. However, melamine does have a place and a purpose, and if you know how to build with melamine, you can produce some budget-friendly spaces.

Some components may be substituted if you can’t source them.  Use your best MacGyvering skills to figure it out.

When we describe a language as type-checked, we mean that the language won't let you perform operations invalid for the type. Neither statically nor dynamically typed languages will let you multiply strings together, call a number in the place of a function, etc. A language without type checking would let you do all of those things without complaint.

At the same time, details about programming language semantics are quite precise and when articles like this get things sort of wrong, it just leads to more confusion.

Conversely, the more dynamically typed the language is, the less I am using an IDE and the more I am using a text editor. Of course, my productivity plummets at that point. Refactoring becomes more difficult and more (completely) reliant on unit tests to ensure they are done properly.

Forwarding events from the native element through the wrapper element comes with a cost, so to avoid adding extra event handlers only a few are forwarded. For all elements except <br> and <hr>, on:focus, on:blur, on:keypress, and on:click are forwarded. For input and textarea, on:input and on:change are also forwarded. For audio and video, on:pause and on:play are also forwarded.

Instead of bind:this={ref}, use bind:el={ref}. this points to the wrapper component, el points to the native element

This works in my application where there's only one shadow-dom at the time, but it's not a generic solution.

As a work-around I know add a listener to the document-head and move what gets added to the shadow-root.

Can you make Svelte create an open shadowRoot? You can then move it yourself (client-side)

The devs clearly took a very conscious choice that broad, wandering exploration should be core to the game - to the extent that they want you to regularly have no idea where you're supposed to go (or indeed, what you're supposed to do when you get there), within environments that are often vastly sprawling. I've rarely seen a game with such minimal, indistinct signposting (sometimes nothing at all) to nudge players in the right direction.

An #each tag can loop anything with a length property, so: {#each {length: 3} as _, i} <li>{i + 1}</li> {/each} will also work, if you prefer.

Note:

this implies an array of arrayLength empty slots, not slots with actual undefined values

Array.from(Array(10).keys()) //=> [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]

https://hypothes.is/search?q=tag:'0-origined+index'

Sigh why was such a standard feature like resizable columns that have been super simple to do in desktop apps for 15+ years not added to css3/html5

mRNA vaccine effectiveness of full immunization (≥14 days after second dose) was 90% against SARS-CoV-2 infections regardless of symptom status

The vaccines aren't a force field that ward off all things COVID-19. They were given the greenlight because they greatly lower your chance of getting seriously ill or dying. But it was easy for me — and I'm not the only one — to grab onto the idea that, after so many months of trying not to get COVID-19, that the vaccine was, more or less, the finish line. And that made getting sick from the virus unnerving.

I had a breakthrough case of COVID-19 — despite my two shots of the Pfizer vaccine, the second one in April.

the realities of our still-raging pandemic, where even the vaccinated can get sick

Whether this game is ever finished or not isn't entirely relevant, the game is vastly inferior to Spore or any of the games from the Sparkle series, but costs more!

I hope this validates (😉) the use of TypeScript and Svelte enough to entice you to try it out for yourself!

and later use Sanity to store our data

The classic SPA example is a to-do list. But, you know what? I don't like to-do lists. They make me think about all the things I have to do, many of which I don't want to do.So why don't we make a To-Don't List app? That way we can list all the things we're not going to do. Ever.

TypeScript is an extension of JavaScript. You can think of it as JavaScript with a few extra features. These features are largely focused on defining the type and shape of JavaScript objects. It requires that you be declarative about the code you're writing and have an understanding of the values your functions, variables, and objects are expecting.While it requires more code, TypeScript is a fantastic means of catching common JavaScript bugs while in development. And for just that reason, it's worth the extra characters.

As a bonus, you have the option of choosing a particular version of JavaScript to target when compiling, so you can use updated JavaScript features, but still, maintain legacy browser support (if you're into that sort of thing)!

React, on the other hand, often requires a fair amount of boilerplate code, even for simple interactions.

The current supported languages out-of-the-box are Sass, Stylus, Less, CoffeeScript, TypeScript, Pug, PostCSS, Babel.

svelte-preprocess doesn't do any kind of type-checking, it just transpiles your ts into js (see it here). If you want to fail your build when a type error is found, you can use svelte-check.

Note: If you want to transpile your app to be supported in older browsers, you must run babel from the context of your bundler.

// No need for babel to resolve modules modules: false,

due to the fact that the pre-processor handles sections independently this cannot reliably be done there.

It is advised to inline any css @import in component's style tag before it hits css-loader. This ensures equal css behavior when using HMR with emitCss: false and production.

hotOptions

while we figure out how to best include HMR support in the compiler itself (which is tricky to do without unfairly favoring any particular dev tooling)

Webpack's resolve.mainFields option determines which fields in package.json are used to resolve identifiers. If you're using Svelte components installed from npm, you should specify this option so that your app can use the original component source code, rather than consuming the already-compiled version (which is less efficient).

Code that is needed to create the output and the output itself is hard to read because of all the workarounds we have to use, especially around shadowed variables and control flow

Any idea what release this will be a part of?

This is the greatest PR I've ever seen in my life (well, in the last month anyways)

Couldn't start client Svelte

Look at local job ads and see what they want.

Do you have practical skills? Can you build useful things?

Don't get me wrong, you need to know your stuff technically. But at the end of the day, the interviewer is asking themselves, “would I like to work with this person ?”

I would suggest focus on interview skills. It doesn't matter how good you are if you can't communicate that to the interviewer.

I was able to secure my current full time job because I was the best communicator and had one of the best interviews. I know my coding skills were no where near other candidates but I was told that they couldn’t communicate well.

They are deliberately dumbing the browser down further and further and it'll probably end up eventually becoming completely unuseable because of this.

(They blame Chrome's "feature" addition treadmill, where "they keep adding stupid kitchen sinks for the sole and only purpose to make others unable to keep up.")

"types": ["node", "svelte"

I think, if <svelte:body> is for adding events, it should apply actions too.

I have never seen the @Stale bot or any directly equivalent to it achieve a net positive outcome. Never. It results in disgruntled people, extra expenditure of effort (for reporters and maintainers), real stuff getting lost when people get fed up with poking the bot (I have no intention of poking it further), and more extensive filing of duplicates. You say a simple comment dismisses it, but it doesn’t—it only does this time. Next time, it continues to annoy. This is an issue tracker. Use labels, projects, milestones and the likes for prioritising stuff. Not sweeping stuff under the carpet.

It is an issue tracker but we don't have a backlog, or planning sessions, or a project board. Or the resources to even triage and tag effectively. If it is important someone will respond / reopen, popular issues are exempt from the bot, we can't fix everything and this is pretty much our only view on stuff that need to be addressed. We need to make some attempt to make sure that everything is still relevant and reduce the noise to a degree where we can actually manage it. I understand the trade-offs with stale bots but we don't have many options. I appreciate your experiences but that doesn't make them a fact. We have discussed this internally and this is what we are doing. If you have any other actionable alternatives outside of saying the bot is bad then we are all ears.

Closing issues doesn’t solve anything. Closing issues in GitHub just sweeps them under the carpet and helps everyone to forget about them, which is just not what you want—the fact that GitHub search excludes closed items by default is a large part of the problem with it. As applied to software projects with general-purpose issue trackers, the @Stale bot is fundamentally phenomenally bad idea, a road paved with good intentions. I presented an actionable alternative: labels. Possibly automatically applied, but it’s certainly better to spend a little bit of time on manual triage. It honestly doesn’t take long to skim through a few hundred issues and bin them into labels. 609 open issues? That’s honestly not a problem. Not at all. There’s nothing wrong with having a large number of issues open, if they do correspond to real things—even things that you may not expect to get to for years, if ever, because that might change or someone might decide they want to deal with one. Closing issues that aren’t dealt with is bad. Please don’t do it.

This is the wrong place for this conversation though.

Most issues have been manually labelled as stale rather than automated and closure will be manual too, so we have time to think.

What steps did you take to get to that point? Did you create a project from a template? Which template?

"paths": { "@/*": ["*"]}

From my point of view, this approach will help you to write cleaner code. Also, it will help to maintain the project. For instance, moving a file from the current directory to another will cause fewer problems, because every file uses an absolute path instead of a relative one. Last but not least, it helps you during development.

alias: { '@': path.resolve(__dirname, 'src'),}

Use this to load modules whose location is specified in the paths section of tsconfig.json when using webpack. This package provides the functionality of the tsconfig-paths package but as a webpack plug-in. Using this plugin means that you should no longer need to add alias entries in your webpack.config.js which correspond to the paths entries in your tsconfig.json. This plugin creates those alias entries for you, so you don't have to!

Notice that the plugin is placed in the resolve.plugins section of the configuration. tsconfig-paths-webpack-plugin is a resolve plugin and should only be placed in this part of the configuration. Don't confuse this with the plugins array at the root of the webpack configuration object.

The declarations you make in the tsconfig.json are re-stated in the webpack.config.js. Who wants to maintain two sets of code where one would do? Not me.

When I look at the tsconfig.json and the webpack.config.js something occurs to me: I don't like to repeat myself. As well as that, I don't like to repeat myself. It's so... Repetitive.

Let's not get over-excited. Actually, we're only part-way there; you can compile this code with the TypeScript compiler.... But is that enough?I bundle my TypeScript with ts-loader and webpack. If I try and use my new exciting import statement above with my build system then disappointment is in my future. webpack will be all like "import whuuuuuuuut?"You see, webpack doesn't know what we told the TypeScript compiler in the tsconfig.json.

import * as utils from '../../../../../../../shared/utils';

Which do you prefer? If the answer was "the first" then read no further. You have all you need, go forth and be happy.

webpack-bot commented on Nov 13, 2020 For maintainers only: webpack-4 webpack-5 bug critical-bug enhancement documentation performance dependencies question

This is not dumb at all. It is exceedingly common to use aliases. It's not about being lazy, it's about writing portable code.

Saying that web devs used to be fine with relative imports is like saying that human beings used to be fine living without refrigerators. Sure we did. But was it better than it is now? No. No, it wasn't.

config: path.resolve(__dirname, '../config'), vue: 'vue/dist/vue.js', src: path.resolve(__dirname, '../src'), store: path.resolve(__dirname, '../src/store'), assets: path.resolve(__dirname, '../src/assets'), components: path.resolve(__dirname, '../src/components'), '@': path.resolve(__dirname, '../src'),

alias: { _self: path.join(__dirname, 'src/web'), _shared: path.join(__dirname, 'src/shared'), _components: path.join(__dirname, 'src/web/components'), _helpers: path.join(__dirname, 'src/web/helpers'), _layers: path.join(__dirname, 'src/web/layers'), _mutations: path.join(__dirname, 'src/web/mutations'), _routes: path.join(__dirname, 'src/web/routes') }

alias: { '@components': path.join(srcDir, 'components'), '@modules': path.join(srcDir, 'modules'), '@store': path.join(srcDir, 'store') }

Aliases are absolute nonsense for resolving imports. If you don't want to type ../ consider using something like path.resolve(__dirname, '../src') so you can do import Stuff from 'client/components/stuff'; // relative to root of project instead of: import Stuff from 'COMPONENTS/stuff'; // this is dumb

alias: { '@shared': path.dirname(require.resolve('app')), '~': path.join(fs.realpathSync(process.cwd()), 'app'), },

In this example, @shared is the package, ~ is the project. I wouldn't do it this way in the future, but I know this configuration works.

This particular project has a differentiation between a package's app/ folder and the current project's app/ folder.

alias: { Library: path.resolve(__dirname, "root/library/"), Single: path.resolve(__dirname, "root/test.js"), },

alias: { Single$: path.resolve(__dirname, "root/test.js"), },

Gems use a period and packages use a dot

(Gems use a period and packages use a dot between the main version number and the beta version.)

Update API usage of the view helpers by changing javascript_packs_with_chunks_tag and stylesheet_packs_with_chunks_tag to javascript_pack_tag and stylesheet_pack_tag. Ensure that your layouts and views will only have at most one call to javascript_pack_tag or stylesheet_pack_tag. You can now pass multiple bundles to these view helper methods.

If you fail to changes this, you may experience performance issues, and other bugs related to multiple copies of React, like issue 2932.

What's the reasoning behind this change?

TylerRick

Yeah I don’t think we will find something that works for everyone in all cases. But Webpacker is quite flexible with the setup it has now. Easy to change!

I feel like app/packs (or something like it) is a good name because it communicates to developers that it's not just JavaScript that can be bundled, it's also CSS, images, SVGs — you name it. I realize what can be bundled is wholly dependent on the bundler you use, but even esbuild supports bundling CSS. So couldn't this possibly be confusing?

Analytics modules that run in the background, monitor user interaction, and send the data to a server.

Many jQuery plugins attach themselves to the global jQuery object.

A polyfill for example, might not do anything, because it finds that the feature that it enables is already supported by the browser.

A module with side-effects is one that changes the scope in other ways then returning something, and it's effects are not always predictable, and can be affected by outside forces (non pure function).

Import a module for its side effects only Import an entire module for side effects only, without importing anything. This runs the module's global code, but doesn't actually import any values.

The important part I have come to notice is <script type="module"></script> make sure you add that otherwise you will get that error.

I still don't understand the difference between a script and a module

Tailwind automatically removes all unused CSS when building for production

I’ve written a few thousand words on why traditional “semantic class names” are the reason CSS is hard to maintain, but the truth is you’re never going to believe me until you actually try it.

If you can suppress the urge to retch long enough to give it a chance, I really think you'll wonder how you ever worked with CSS any other way.

Upgrade to Webpacker 6

Class constructor ServeCommand cannot be invoked without 'new'

In 3.1.0, we used oneOf option which solved this problem but then loaders which were using multiple transformation started failing (erb loader) since it was using first matching loader from the list.

Thanks @gj ! That's the best config help response I've ever gotten--changed the regex as you outlined, removed the md.js file I had added, and updated environment.js you post and it worked perfectly.

WARNING in ./app/javascript/components/ComponentLibrary/Docs/Intro.md Module parse failed: Unexpected character '#' (1:0) You may need an appropriate loader to handle this file type.

though we recommend Jest as our preference, the library works with any framework