Merge upstream

.github/workflows/node.js.yml

@@ -27,7 +27,7 @@ jobs:
       with:
         node-version: 16.x
     - name: Install dependencies and build site
-      run: npm i -g pnpm@7 && pnpm up && pnpm i --shamefully-hoist && webpack --bail
+      run: npm i -g pnpm@7 && pnpm up && pnpm i --shamefully-hoist && NODE_ENV=production webpack --bail
     - name: Upload artifact
       uses: actions/upload-pages-artifact@v1
       with:
@@ -36,7 +36,7 @@ jobs:
   deploy:
     environment:
       name: github-pages
-      url: 'https://penguinmod.site/project'
+      url: 'https://penguinmod.com/project'
     runs-on: ubuntu-latest
     needs: build
     steps:

.gitignore

@@ -13,7 +13,11 @@ npm-*
 /.opt-in
 !build/
 !dist/
+build/*
+yarn.lock
 
 # Generated translation files
 /translations
 /locale
+src/lib/tw-translations/new-generated-translations.json
+src/lib/tw-translations/merged-translations.json

.npmignore

@@ -1 +1,16 @@
 
+# NPM
+/node_modules
+npm-*
+
+# Testing
+/.nyc_output
+/coverage
+/test
+
+# Build
+/.opt-in
+/build
+
+# generated translation files
+/translations

.vscode/settings.json

@@ -1,5 +1,8 @@
 {
     "yaml.schemas": {
         "https://gitpod.io/schemas/gitpod-schema.json": "file:///workspace/penguinmod.github.io/.gitpod.yml"
+    },
+    "files.associations": {
+        "*.css": "scss"
     }
 }

FORKING.md

@@ -0,0 +1,26 @@
+This file contains instructions on what you should do upon forking PenguinMod.
+
+You don't HAVE to follow this document but it'll prevent a lot of confusion for your users and likely prevent your mod from being blacklisted from our internal servers.
+
+# Branding changes
+Update any labels or text that says "PenguinMod" and put your mod's name.
+You shouldn't do this for IDs or anything like that.
+
+You should also update your credits & privacy policy pages. We didn't work on your mod, you just made an extension of ours.
+
+Update any links to our github to yours so people can find the source code. Also make sure to update links that you have your own version of like feedback, docs, or packager.
+
+### The "don't do that" section
+Don't remove any credit to Scratch, TurboWarp, or PenguinMod. That's just not cool.  
+Imagine if someone just forked your copy and pretended they made it all themselves.
+
+I'm not legal advice but you should probably not change the license or make the public repos you forked into private ones.
+
+To my knowledge, you can't just do that without some problems.
+
+# Server changes
+Unless you plan on keeping your mod 100% compatible with PenguinMod, please remove the Upload button and any project sharing features.
+
+Our APIs are only built for PenguinMod and therefore will likely end up breaking in your mod at some point or another.
+
+We also do not allow projects that only work outside of PenguinMod so if you end up having a lot of uploads from your site, then we'll have to block your site from being able to use the project API.

README.md

@@ -6,7 +6,7 @@ to run snail ide on your computer, you'll need nvm (node version manager).<br>
 type ``nvm install 16`` then ``nvm use 16`` in your terminal. (if your on windows, accept the uac prompts)<br>
 then your gonna need pnpm. there may be other ways to install snail ides dependencies without pnpm, but right now you'll need it. you can install it by typing ``npm install -g pnpm``. <br>
 after you install pnpm, clone the snail ide gui with ``git clone https://github.com/snail-ide/snail-ide.github.io``.<br>
-then run ``pnpm i --shamefully-hoist``. after that, you can type ``npm start`` or ``pnpm start`` or ``yarn start`` if you have yarn.<br/>
+then run ``NODE_OPTIONS=--openssl-legacy-provider pnpm i --shamefully-hoist``. after that, you can type ``npm start`` or ``pnpm start`` or ``yarn start`` if you have yarn.<br/>
 if you want to use node 17+ , you'll have to add the enviroment variable `NODE_OPTIONS` with the content `--openssl-legacy-provider` before the start command.<br/>
 on linux/github codespaces you can do that by running the command `export NODE_OPTIONS=--openssl-legacy-provider`.