Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@e3c-summer-worker/navigation

Package Overview
Dependencies
Maintainers
0
Versions
30
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@e3c-summer-worker/navigation

Making our custom headers is a bit involved. We have to copy a lot of HTML code into the scripts, and it's confusing and difficult to debug if something changes and goes wrong, especially if our only text editor is the one built into Squarespace.

  • 2.3.4
  • latest
  • npm
  • Socket score

Version published
Weekly downloads
0
decreased by-100%
Maintainers
0
Weekly downloads
 
Created
Source

Navigations

Making our custom headers is a bit involved. We have to copy a lot of HTML code into the scripts, and it's confusing and difficult to debug if something changes and goes wrong, especially if our only text editor is the one built into Squarespace.

Making the navigation in another component where you ethen import it is easier to debug and move around; you copy less code between pages and the development process is better if you're using something like VSCode.

We are using this folder to specifically host the desktop and mobile navigation component, that goes inside #headerNav and #sidecarNav in the Squarespace page, respectively.

The header code in public/index.html is almost exactly what you'd see copy and pasted into Squarespace (instead of importing the local .js file we use JSDelivr, and we need to add the contents in and styles.css.

Note that we are using yarn workspaces, so the installations will be mostly consolidated at a top-level node_modules/ folder.

Important

The site.css is the squarespace compiled css, and the styles.css are our styles.

Local Development

yarn
yarn start

Note that the styles will be quite a bit different than production, this is because I only copied a subset of the HTML into our public/ html file. The important thing is that the navigation bar is functional.

Also, when you switch to Desktop to Mobile view, refresh the page to get the functional navigation bars. Not sure why this is the case, maybe I didn't download all the files.

Production Build

yarn build

Usage

V2

In v2, only the import is needed.

<script src="https://cdn.jsdelivr.net/npm/@e3c-summer-worker/navigation@2/build/navigation.js"></script>

V1

<script src="https://cdn.jsdelivr.net/npm/@e3c-summer-worker/navigation@1/build/mobilenav-elm.js"></script>
<script src="https://cdn.jsdelivr.net/npm/@e3c-summer-worker/navigation@1/build/desktopnav-elm.js"></script>
<script>
    window.onload = function () {
        // desktop navigation
        const headerNav = document.getElementById('headerNav');
        const app_d = Elm.DesktopNav.init({ node: headerNav });

        // mobile navigation
        const sidecarNav = document.getElementById('sidecarNav');
        const app_m = Elm.MobileNav.init({ node: sidecarNav });
    }
</script>

FAQs

Package last updated on 14 Oct 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc