Giter Club home page Giter Club logo

fxsync's Introduction

fxsync

fxsync is a bundler that allows you to import React components from your existing projects into a Framer X file without changes to your existing code.

Installation

npm install -g @jamsesso/fxsync

Important: Node.js >= 10.12.0 is required!

Usage

Setup

First, create a .framerx file that you want to inject your project's components into.

Next, In your npm project, annotate each component file you want to inject into your Framer X design with the @framerx <component name> pragma. For example:

/** @framerx MyProductionButton */
import React from 'react';

function Button({children, onClick}) {
  return <button type="button" onClick={onClick}>{children}</button>;
}

export default Button;

Important: The component name in the @framerx pragma does not need to match the component name defined in the file, but it must be a valid JSX identifier. Your component must also be the default export in the file.

The name you specify in the pragma is the name that the component will have inside your Framer X design file (in this case it is MyProductionButton; see line 1 of the previous example).

Bundling your Components

Next, run fxsync with the path to your npm project (the directory containing the project's package.json) and the path to your existing .framerx file. This works best if you do not have the Framer file open in Framer while this command is executing.

fxsync <path to your npm project> <path to your .framerx file>

This will build a common-js compatible file named after your npm project (name in the package.json file) and inject it into your .framerx file at code/lib/<your npm project name>.js.

fxsync can be run any number of times against the same .framerx file. When your production React code is updated, re-run the fxsync bundler to update the components in Framer X.

Integrating Components into Framer X

Now that your production code is available inside of your Framer X design file, we can use them in our designs.

In Framer X, create a new component from Code. This will generate a file that you can modify. For this example, I am going to create a code component called MyFramerXButton:

import * as React from "react";
import { PropertyControls, ControlType } from "framer";

// Import your production components.
// my-project-name should be replaced by the name from your 
// project's package.json file.
import {MyProductionButton} from './fxsync/my-project-name';

type Props = { text: string };

export class MyFramerXButton extends React.Component<Props> {
  static defaultProps: Props = {
    text: "Hello World!"
  };
  
  static propertyControls: PropertyControls<Props> = {
    text: { type: ControlType.String, title: "Text" }
  };

  render() {
    return <MyProductionButton>{this.props.text}</MyProductionButton>;
  }
}

API

fxsync offers an API for running the build in code.

const fxsync = require('fxsync');
fxsync('/path-to-project', '/path-to-design.framerx');

Testing & Issues

This bundler was developed against a project that uses create-react-app and styled-components. It may not work for every type of project structure at this point.

If you find issues, I will do my best to explain how this bundler needs to be changed in order to support your project's requirements - however, it will likely be up to you to submit a PR with a fix.

fxsync's People

Contributors

jamsesso avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

Forkers

pouncyisdead

fxsync's Issues

Support for Framer X folder-based projects

Framer X has the ability to save a design file as a directory, which helps with things like source control. It is currently hidden behind a key combination while saving, so is not yet considered GA. fxsync only works with the .framerx design file zip currently. We should support the folder format for projects.

Support custom build scripts

Allow projects to provide their own build steps - these builds must produce Framer X-compatible files (such as a CJS bundle). fxsync could then handle the injection of the build artifacts into the design file.

Detect project type and use an appropriate build

Right now, fxsync uses create-react-library meant for apps that were bootstrapped using create-react-app. In order to support more projects in the future (even outside of the React world), we should add the concept of "build strategies".

A build strategy in this context would be a module that was responsible for determining the appropriate CJS build for the project. Today, there would only be a single strategy - the create-react-app strategy (potentially detected by a a dependency on react-scripts?)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.