In package-lock.json of the project that consumes your package as a dependency, ensure your package has "hasInstallScript": true. On npm ci or npm install, npm looks for the existence of this flag in package-lock.json rather than scanning each library’s package.json for “preinstall”, “install”, or “postinstall” scripts.

If your package is part of an organization, then it may be due to this bug: https://github.com/npm/cli/issues/4821

Or this bug: https://github.com/npm/cli/issues/5380

For what it’s worth, I am using both a custom registry with packages under an organization.

If you have a question or feedback, please post it in the comment section below.

If you like this extension, please support my other work.

Support DeepL as well for providing us a great alternative to Google Translate. I am not affiliated in any way with DeepL.

Download Links

For the Brave/Chrome extension, click here.

For the FireFox add-on, click here.

Frequently Asked Questions (FAQ)

Nothing yet!

To do so, you must assign the event prop of the IonPopover with the event value.

However, since React also nullifies all event properties due to Event Pooling and Ionic is looking for the event target to help position the IonPopover, you will first have to persist the event.

Extending the documentation‘s example to enable relative positioning of the popover in React, note the differences:

1. showPopoverEvent local state defaults to null, and will hold an event object.
2. isOpen still expects a boolean, and is true if showPopoverEvent is not empty.
3. IonButton onClick must call persist on the event, and we set the local state to store the event.
4. Finally, the event prop on IonPopover is set to the event stored in the local state.

import React, { useState } from 'react';
import { IonPopover, IonButton } from '@ionic/react';

export const PopoverExample: React.FC = () => {
  const [showPopoverEvent, setShowPopoverEvent] = useState(null);

  return (
    <>
      <IonPopover
        isOpen={!!showPopoverEvent}
        onDidDismiss={() => setShowPopoverEvent(null)}
        event={showPopoverEvent}
      >
        <p>This is popover content</p>
      </IonPopover>
      <IonButton onClick={(e) => { e.persist(); setShowPopoverEvent(e); }}>
        Show Popover
      </IonButton>
    </>
  );
};

ion-searchbar.collapsible {
  width: 55px; // match hard-coded padding-inline-end when collapsed
               // .searchbar-input {
               //   @include padding(6px, 55px);
               // }

  transition: width 0.5s ease-in-out;
  --border-radius: 4px;

  .searchbar-input.sc-ion-searchbar-md {
    transition-property: padding-inline-end, -webkit-padding-end;
    transition-duration: 0.5s;
    transition-timing-function: ease-in-out;
  }

  &.searchbar-has-focus,
  &.searchbar-has-value {
    width: 100%;
  }

  &:not(.searchbar-has-focus):not(.searchbar-has-value):hover input {
    cursor: pointer;
    background: var(--ion-color-step-100);
  }

  &:not(.searchbar-has-focus),
  &:not(.searchbar-has-value) {
    .searchbar-input.sc-ion-searchbar-md {
      -webkit-padding-end: 0;
      padding-inline-end: 0;
    }
  }
}

Then add the class collapsible to your ion-searchbar.

constructor(
  private alertCtrl: AlertController,
  private animationCtrl: AnimationController
) {

}

private async showAlert() {
  const alert = await this.alertCtrl.create({
    message: 'Hello world',
    enterAnimation: (baseEl: any, opts?: any) => {
      return(this.animationCtrl
        .create()
        .addElement(baseEl.querySelector('.alert-wrapper'))
        .duration(250)
        .keyframes([
          { offset: 0, opacity: '0' },
          { offset: 1, opacity: '1' }
        ]));
    }
  });

  await alert.present();
}

1. Right-click the link you want to follow
2. “Copy link location” (FireFox) or “Copy Link URL” (Chrome)
3. Right-click the address bar
4. “Paste & Go” (FireFox) or  “Paste and go to …” (Chrome)

That’s it, and now you’ve learned two context menu shortcuts in your web browser as well.

*     *     *

Why does it work?

Well you may have figured that out by reading another 2013 blog post (appears currently as a high ranked search result) that is technically correct saying that Quora.com tracks referring URLs.  If you were referred to the current Quora page from another Quora page, it will present you with a sign-in/create account overlay. That 2013 blog post provides a woefully unnecessary solution of using a plug-in to get around the problem.

If you directly enter the URL into the address bar, no referral URL is provided in the header sent to Quora by the browser.  This principle applies to anything that tracks by referring URL.  If you are super-paranoid and don’t want your browsing habits to be tracked, especially by search engines, you may want to start copying URLs from your search results and pasting them directly into the browser address bar.

Long version
How we arrived at the above command via Gitea’s docs:

docker exec -u <OS_USERNAME> -it -w <--tempdir> $(docker ps -qf "name=<NAME_OF_DOCKER_CONTAINER>") bash -c '/app/gitea/gitea dump -c </path/to/app.ini>'

Here’s what you should replace each <…> with, assuming you installed from Docker following the instructions here (note where docker mounts the container’s “data” folder is found under “services:”/”server:”/”volumes:”, it is likely the path ./gitea, relative to where your docker-compose.yml resides):

<OS_USERNAME>: Look inside gitea/conf/app.ini in the folder where docker mounts its “data” folder (./gitea/gitea/conf/app.ini relative to where your docker-compose.yml resides). It is the value matching RUN_USER, and this is usually git unless you changed it.

<–tempdir>: Leaving it as is will store it in /tmp in the container, which is not mounted to a local folder.  Create a “backup” directory ./gitea/gitea/backup relative to where your docker-compose.xml resides. Replace <–tempdir> with /data/gitea/backup, as this is a path referenced in the container.

<NAME_OF_DOCKER_CONTAINER>: run docker ps and note the NAME (last column) containing gitea.  This is usually “gitea_server_1”.

</path/to/app.ini>: This is a path referenced in the container, so it needs to use /data/gitea/conf/app.ini (i.e. this points to the local ./gitea/gitea/conf/app.ini relative to where your docker-compose.yml resides).

Wait … why should it cost you anything at all if you will be doing all the heavy lifting and event organizing?

You’re already volunteering your time and energy. Don’t volunteer more money than you need to too.

Help spread the word about Casual Events — an event platform that is free for everybody.  (Except me of course, the developer. I still have to pay server costs and invest hundreds of hours of my labour. But if you join will be worth it!)

However, without the service worker registered, navigation requests are not intercepted and sent to the PWA. In other words, if a user has never ran the PWA yet in his or her browser, and he or she tries to navigate to a specific page in the PWA (e.g. https://mywebapp.abc/foo/bar), your web server will likely return a 404 error. We would like to serve the PWA first, then relay the /foo/bar path to the Angular router.

Nginx config solution

If you have access and can configure the static serving of files on your web server, you will want to use the try_files directive:

location / {
  try_files $uri $uri/ /index.html;
}

Using this directive, Nginx will attempt to serve the static file based on the URI path (e.g. /images/foo.png will load correctly), but in all other instances where it cannot find a static file to serve if it is instead a PWA Angular route (e.g. /foo/bar), it will serve index.html of your PWA. This will eliminate all 404 errors and will serve up the PWA entry page, retaining the “404” URL in the browser (/foo/bar) so the Angular router can handle it.

The downside to this is that all legitimate 404 errors now always serve the PWA’s index.html, which may not be desirable. Say your server was actually missing /images/foo.png, then it will instead serve index.html in its place rather than returning a 404.

404 page solution

Another possible solution is to create a custom 404 page containing the following Javascript that accomplishes three things:

1. Checks if there is a ngsw-worker.js to register.
2. Loads the PWA in an iframe, so that the service worker is installed.
3. Once the iframe is done loading, refresh the page with the intended URL. The PWA router will now pick up the navigation request to /foo/bar and transition to the correct page after load.

      var request = new XMLHttpRequest();  

      request.open('GET', '/ngsw-worker.js', true);
      request.onreadystatechange = function(){
        if (request.readyState === 4){
          if (request.status === 200) {
            var iframe = document.createElement('iframe');

            document.body.append(iframe);

            iframe.style.setProperty('position', 'fixed');
            iframe.style.setProperty('left', '0');
            iframe.style.setProperty('top', '0');
            iframe.style.setProperty('width', '100%');
            iframe.style.setProperty('height', '100%');
            iframe.style.setProperty('border', '0');
            iframe.style.setProperty('background-color', '#f7f7f7');

            iframe.src = '/';
            iframe.onload = function() {
              location.reload();
            };
          }  
        }
      };
      request.send();

As of the time of this writing, this alternate solution does not work with FireFox but works well in Chrome.

Casual Events is a new platform that needs your help to grow. Since it is maintained by one person (me) you don’t have to subsidize conglomerate salaries to use the platform. Additionally, you’ll have the opportunity to have the app tailored to your needs since the platform is young and you will have direct one-on-one access with the developer for future features and fixes.

Nearly everything you do with Meetup can be done with Casual Events. We just need to spread the word!  You can access the app on your iPhone, Android phone or on any other device or desktop via the web app.

Best of all, the platform is ethical — something you won’t find with big tech and Silicon Valley. The site and ads don’t track you with cookies. It is purposely dissociated from social media so that your privacy is protected: no data mining, no invasive snooping, no selling your habits to third parties, no Big Brother.