Owen Buckley thescientist13

## single-file-web-component.html
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <title>Single File Web Component</title>
</head>
<body>
  <template id=single-file>
    <style>
      h1 {

## esm-package.md

      
              1 file
            
          
              200 forks
            
          
              7 comments
            
          
              2769 stars
            
          
                sindresorhus
                / esm-package.md
            
            
              Last active
              April 23, 2024 09:02
            
              
                Pure ESM package
              
          
    Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:

Use ESM yourself. (preferred)

  Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.


## 10ThingsWrongWebComponents.md

      
              1 file
            
          
              0 forks
            
          
              2 comments
            
          
              17 stars
            
          
                arei
                / 10ThingsWrongWebComponents.md
            
            
              Last active
              February 20, 2024 03:16
            
              
                10 Things You Are Doing Wrong in your Web Components
              
          
    10 Things You Are Doing Wrong in your Web Components

Web Components enable custom element creation and sharing on a whole new level that has not really been seen to date but is so desperately needed.  Developers of everything from simple webpages to complex applications are using Web Components to deliver new functionality, new behaviors, and new designs. Web Components are a big part of the future of the web.
There are lots of articles detailing how to build a basic Web Component, but almost no article details how to solve some of the gotchas once you start down that road.  That's what this article serves to do; point out some of the things every Web Component developer is overlooking and to which they should probably be giving more consideration.
1). Not Using a Web Component Framework

The APIs which make up the Web Components standards (Custom Elements, ShadowDOM, etc) are intentionally low level APIs. As such they are not always the most clear or concise in their understandability. Additionally,

  
## angular-cli-node-js-typescript-rxjs-compatiblity-matrix.csv

          
            Angular CLI version
            Angular version
            Node.js version
            TypeScript version
            RxJS version

            
              ~16.0.0
              ~16.0.0
              ^16.13.0 || ^18.10.0
              	>=4.9.5 <5.1.0
              ^6.5.5 || ^7.4.0

            
              ~15.2.0
              ~15.2.0
              ^14.20.0 || ^16.13.0 || ^18.10.0
              	>=4.8.4 <5.0.0
              ^6.5.5 || ^7.4.0

            
              ~15.1.0
              ~15.1.0
              ^14.20.0 || ^16.13.0 || ^18.10.0
              	>=4.8.4 <5.0.0
              ^6.5.5 || ^7.4.0

            
              ~15.0.5
              ~15.0.4
              ^14.20.0 || ^16.13.0 || ^18.10.0
              	~4.8.4
              ^6.5.5 || ^7.4.0

            
              ~14.3.0
              ~14.3.0
              ^14.15.0 || ^16.10.0
              	>=4.6.4 <4.9.0
              ^6.5.5 || ^7.4.0

            
              ~14.2.0
              ~14.2.0
              ^14.15.0 || ^16.10.0
              	>=4.6.4 <4.9.0
              ^6.5.5 || ^7.4.0

            
              ~14.1.3
              ~14.1.3
              ^14.15.0 || ^16.10.0
              	>=4.6.4 <4.8.0
              ^6.5.5 || ^7.4.0

            
              ~14.0.7
              ~14.0.7
              ^14.15.0 || ^16.10.0
              	>=4.6.4 <4.8.0
              ^6.5.5 || ^7.4.0

            
              ~13.3.0
              ~13.3.0
              ^12.20.2 || ^14.15.0 || ^16.10.0
              >=4.4.4 <4.7.0
              ^6.5.5 || ^7.4.0

## prepack-gentle-intro-1.md

      
              1 file
            
          
              26 forks
            
          
              14 comments
            
          
              638 stars
            
          
                gaearon
                / prepack-gentle-intro-1.md
            
            
              Last active
              February 13, 2024 14:30
            
              
                A Gentle Introduction to Prepack, Part 1
              
          
Note:
When this guide is more complete, the plan is to move it into Prepack documentation.

For now I put it out as a gist to gather initial feedback.

A Gentle Introduction to Prepack (Part 1)

If you're building JavaScript apps, you might already be familiar with some tools that compile JavaScript code to equivalent JavaScript code:

Babel lets you use newer JavaScript language features, and outputs equivalent code that targets older JavaScript engines.


## docker-shell.sh
docker run -ti -v $(pwd):/tmp DOCKER_IMAGE /bin/bash

## get_streetview_image.py
import requests
from PIL import Image
from io import BytesIO
import os
import pandas as pd

# get crosswalk dataset
newport_crossings_url = 'https://raw.githubusercontent.com/NewportDataPortal/sidewalk-map/development/npt-sidewalk-street-intersections.geojson'
crossing_response = requests.get(newport_crossings_url)
crossing_json = crossing_response.json()

## ml-recs.md

      
              1 file
            
          
              65 forks
            
          
              4 comments
            
          
              158 stars
            
          
                bsletten
                / ml-recs.md
            
            
              Last active
              January 24, 2024 19:28
            
              
                Machine Learning Path Recommendations
              
          
    This is an incomplete, ever-changing curated list of content to assist people into the worlds of Data Science and Machine Learning. If you have a recommendation for something to add, please let me know. If something isn't here, it doesn't mean I don't recommend it, I just may not have had a chance to review it yet or not.
I will generally list things in order of easier to more formal/challenging content.
It may feel like there is an overwhelming amount of stuff for you to learn (because there is). But, there is a guided path that will get you there in time. You need to focus on Linear Algebra, Calculus, Statistics and probably Python (or R). Your best bet is to get a Safari Books Online account (https://www.safaribooksonline.com) which you may already have access to through school or work. If not, it is a reasonable way to get access to a tremendous number of books and videos.
I'm not saying you will get what you need out of everything here, but I have read/watched at least some of all of the following an

  
## index.html
<body>
<div id="⚛️"></div>
<script src="https://unpkg.com/react@16.0.0/umd/react.development.js"></script>
<script src="https://unpkg.com/react-dom@16.0.0/umd/react-dom.development.js"></script>
<script src="https://unpkg.com/babel-standalone@6.26.0/babel.js"></script>
<script type="text/babel">
ReactDOM.render(<div>Hello World!</div>, document.getElementById('⚛️'))
</script>
</body>

## datepicker.decorator.js
/**
 * Decorates the ui-bootstrap datepicker directive's controller to allow
 * refreshing the datepicker view (and rerunning invalid dates function)
 * upon an event trigger: `$scope.$broadcast('refreshDatepickers');`
 *
 * Works with inline and popup. Include this after `ui.bootstrap` js
 */
angular.module('ui.bootstrap.datepicker')
    .config(function($provide) {
        $provide.decorator('datepickerDirective', function($delegate) {
	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<title>Single File Web Component</title>
	</head>
	<body>
	<template id=single-file>
	<style>
	h1 {
Angular CLI version	Angular version	Node.js version	TypeScript version	RxJS version
~16.0.0	~16.0.0	^16.13.0 \|\| ^18.10.0	>=4.9.5 <5.1.0	^6.5.5 \|\| ^7.4.0
~15.2.0	~15.2.0	^14.20.0 \|\| ^16.13.0 \|\| ^18.10.0	>=4.8.4 <5.0.0	^6.5.5 \|\| ^7.4.0
~15.1.0	~15.1.0	^14.20.0 \|\| ^16.13.0 \|\| ^18.10.0	>=4.8.4 <5.0.0	^6.5.5 \|\| ^7.4.0
~15.0.5	~15.0.4	^14.20.0 \|\| ^16.13.0 \|\| ^18.10.0	~4.8.4	^6.5.5 \|\| ^7.4.0
~14.3.0	~14.3.0	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.9.0	^6.5.5 \|\| ^7.4.0
~14.2.0	~14.2.0	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.9.0	^6.5.5 \|\| ^7.4.0
~14.1.3	~14.1.3	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.8.0	^6.5.5 \|\| ^7.4.0
~14.0.7	~14.0.7	^14.15.0 \|\| ^16.10.0	>=4.6.4 <4.8.0	^6.5.5 \|\| ^7.4.0
~13.3.0	~13.3.0	^12.20.2 \|\| ^14.15.0 \|\| ^16.10.0	>=4.4.4 <4.7.0	^6.5.5 \|\| ^7.4.0
	import requests
	from PIL import Image
	from io import BytesIO
	import os
	import pandas as pd

	# get crosswalk dataset
	newport_crossings_url = 'https://raw.githubusercontent.com/NewportDataPortal/sidewalk-map/development/npt-sidewalk-street-intersections.geojson'
	crossing_response = requests.get(newport_crossings_url)
	crossing_json = crossing_response.json()
	<body>
	<div id="⚛️"></div>
	<script src="https://unpkg.com/react@16.0.0/umd/react.development.js"></script>
	<script src="https://unpkg.com/react-dom@16.0.0/umd/react-dom.development.js"></script>
	<script src="https://unpkg.com/babel-standalone@6.26.0/babel.js"></script>
	<script type="text/babel">
	ReactDOM.render(<div>Hello World!</div>, document.getElementById('⚛️'))
	</script>
	</body>
	/**
	* Decorates the ui-bootstrap datepicker directive's controller to allow
	* refreshing the datepicker view (and rerunning invalid dates function)
	* upon an event trigger: `$scope.$broadcast('refreshDatepickers');`
	*
	* Works with inline and popup. Include this after `ui.bootstrap` js
	*/
	angular.module('ui.bootstrap.datepicker')
	.config(function($provide) {
	$provide.decorator('datepickerDirective', function($delegate) {